Slashdot Mirror


Retired Mainframe Pros Lured Back Into Workforce

itwbennett writes "Businesses that cut experienced mainframe administrators in an effort to cut costs inadvertently created a skills shortage that is coming back to bite them. Chris O'Malley, CA's mainframe business executive VP, says that mainframe workers were let go because 'it had no immediate effect and the organizations didn't expect to keep mainframes around.' But businesses have kept mainframes around and now they are struggling to find engineers. Prycroft Six managing director Greg Price, a mainframe veteran of some 45 years, put it this way: 'Mainframes are expensive, ergo businesses want to go to cheaper platforms, but [those platforms] have a lot of packaged overheads. If you do a total cost of ownership, the mainframe comes out cheaper, but since the costs of a mainframe are immediately obvious, it is hard to get it past the bean-counters of an organization.'"

24 of 223 comments (clear)

  1. Not a new phenomenon by ls671 · · Score: 5, Interesting

    As early as 2002, I started to half-jokingly tell young co-workers that were asking that they should learn COBOL as a way to insure them a prosperous career. ;-) Back then, most schools were removing or had removed COBOL programming from their course list.

    I was half-jokingly telling them that by 2015 they should be earning 150-200K a year as a simple COBOL developer ;-)))

    See this article from last year saying basically the same thing :

    http://www.computerweekly.com/Articles/2008/08/07/231774/cobol-programmer-shortage-starts-to-bite.htm

    Note: I am to old to start to learn COBOL, this is stuff for young people... ;-)

    --
    Everything I write is lies, read between the lines.
    1. Re:Not a new phenomenon by mikael_j · · Score: 3, Interesting

      Perhaps because COBOL isn't very similar to python, PHP or vbscript?

      (I regularly use python, PHP and vbscript at work and I've messed around with COBOL at home on a few occasions and while the language is by no means hard to grasp it is a bit peculiar and I could never stand working on a large COBOL project.)

      /Mikael

      --
      Greylisting is to SMTP as NAT is to IPv4
    2. Re:Not a new phenomenon by kbrasee · · Score: 3, Informative

      Web "programmer"... Hahaha, good one!

      Web programming != web interface design. Welcome to the 21st century.

    3. Re:Not a new phenomenon by mcrbids · · Score: 4, Funny

      But bloody hell, if I can make six figures writing cobol, I'll grab myself a cobol book and quit this programming job. A sucky day job isn't so bad when it means you can retire a decade earlier than otherwise.

      My advice for new programmers has been exactly this: learn COBOL, study mainframes, move to large cities, make big bucks. Sure, you'll want to gouge your eyes out with a fork, but then you'll be able to afford to have robotic eyes grafted back in!

      As a second, I recommend that they learn Unix skills, c, and databases. Still lots of money there, and your original eyeballs will last longer. (It's the path I chose, and I do quite well for myself)

      --
      I have no problem with your religion until you decide it's reason to deprive others of the truth.
    4. Re:Not a new phenomenon by ls671 · · Score: 5, Funny

      > Why would you higher a "Cobol" coder to program Cobol

      Because most "web programmers" we know of do not know how to spell. Our COBOL programming interface (terminal based) doesn't have auto-completion or auto-correction features so misspelled words cause errors only when the programmer hits the compile key.

      Compiler errors are cryptic and it takes a lot of time to find and fix the misspellings. So even if the logic of the code was flawless (for which we also have doubts), simple spelling errors cost us too much money thus making HIRING web developers a non viable alternative for us.

      --
      Everything I write is lies, read between the lines.
    5. Re:Not a new phenomenon by lgw · · Score: 4, Interesting

      COBOL is an odd beast, with no pointer/references and barely even has the concept of arrays. It makes processing a stream of input records to create a stream of output records, with occasional DB updates along the way, very straightforward. It's fine at text-oriented work and formatting as well (I bet it would work fine to implement an AJAX backend). Anything else, not so much.

      MULTIPLY FOO BY BAR GIVING QUX. - Actual math syntax (never used, I expect, but humorous).

      --
      Socialism: a lie told by totalitarians and believed by fools.
    6. Re:Not a new phenomenon by Greyfox · · Score: 3, Informative
      I was subjected to 3 semesters of that crap in college, which caused me to set my price for doing COBOL programming to $300/Hour (USD). It's an awful language which you write using awful tools in an awful operating system.

      I rather like mainframes in general though. Hell I can at least tolerate Fortran if it comes down to it. COBOL... not so much.

      --

      I'm trying to teach myself to set people on fire with my mind... Is it hot in here?

    7. Re:Not a new phenomenon by Opportunist · · Score: 3, Interesting

      So you don't like working with COBOL. I haven't ever heard of a "small COBOL project".

      --
      We used to have a Bill of Rights. Now, with the rights gone, all we have left is the bill.
    8. Re:Not a new phenomenon by Decker-Mage · · Score: 3, Interesting

      Like you I generally prefer to be referred to as a consultant since it wasn't until recently that I found the proper term (synthesist). I operate across multiple problem domains, engineering disciplines, sciences, etc. By the time I left the Navy, I had trained two other individuals to approach systems analysis and engineering my way and I'm certain they did quite well. The problems are, as I see it: (1) an inability to systematically deconstruct the processes to there core (layered) components, and reengineer them as needed; (2) the inability to delegate to subject matter experts that are available; and (3) the inability to foster teamwork. Usually it's 1 that kills most projects, but 2 & 3 can lead to far larger financial loses as well as losses in prestige and personnel.

      About five years into my naval career, they handed me a key to the front (control) panel to every Harris 300/301 computer and the master password for Pacific Fleet. A Harris system engineer also gave an unexpurgated system generation tape (all the compilers, tools, and documentation were uncut). I never knew where I was going on some days but it was sure fun since it was all about understanding the processes and making them tick correctly be it hardware, software, or people. And teaching, of course!

      --
      "[I]t is a wise man who admits the limits of his knowledge or skill, and that pretending either causes harm." --Terry Go
  2. Cobol vs. Data Entry by c0d3r · · Score: 3, Insightful

    I learned and taught cobol for awhile, and i can say that cobol is not too far from data entry. It is way too much work to do simple things, and it is way too weak of a language for most things. Its functionality is low that it takes a lot of code to implement simple things. The compiler gives you weird error messages. The language is archane. It is a very miserable language to write in, and I wouldn't code in it for less than several hundreds of dollars per hour, just because its so boring and takes way too much typing to do simple things that would be a snap in other languages.

    1. Re:Cobol vs. Data Entry by JPLemme · · Score: 4, Interesting

      And don't forget that in COBOL, not only is all of your data global to your program, in a typical batch cycle all of the data is global to ALL of the programs.

      I used to hate discovering that field XYZ was being modified in jobs that were completely unrelated to XYZ, because the programmer was too lazy to check the appropriate code out of the repository. "Why bother? I can make the change right here and it'll work just fine!"

      My favorite line was "Being on a COBOL dev team is like living in a dorm."

    2. Re:Cobol vs. Data Entry by Qzukk · · Score: 4, Informative

      no worse than C

      Except for C having "+" "-" and "=" instead of "MULTIPLY units AND cost GIVING total"

      If Perl is the archetypal "write only" language, COBOL is the one true "read only" language.

      people are crazy not to get into this field

      The whole point of TFA was that entry level jobs where people could "get in" went away, then all the senior staff retired or expired, leaving the companies with nothing.

      --
      If I have been able to see further than others, it is because I bought a pair of binoculars.
    3. Re:Cobol vs. Data Entry by BluBrick · · Score: 3, Funny

      Hey!

      ***

      I quite enjoyed TSO

      ***

      Oh wait

      ***

      That was ISPF that I enjoyed.

      ***

      --
      Ahh - My eye!
      The doctor said I'm not supposed to get Slashdot in it!
    4. Re:Cobol vs. Data Entry by JPLemme · · Score: 3, Interesting

      They weren't all running in one memory space -- they were all running on one common set of files. For example, you might have a system that accepts 15 files from various other systems, processes those files against a set of master VSAM files and/or against a database, and then creates a set of 15 files that get sent out to other systems. The system itself consists of a series of JCL jobs. Each job consists of multiple COBOL programs and utilities. It's just like bash, except in a way that's nothing at all like bash....

      But because any program which opens a file can change any data contained in the file, it's tempting to make tweaks wherever it's handy. Nobody claims it's good practice, but these systems have been under constant tweaking for 30 or 40 years by dozens of programmers. After the first decade nobody even knows what the programs were supposed to do in the first place. (Especially since they have names like AB1243A, where 3 of the 7 characters identify the application, leaving only 4 characters to describe what the program does.)

      So the typical bug-hunt consists of noticing that a field has the wrong value, and then checking each individual intermediate file from start to finish to see which job changed it. And if you're on a system that doesn't save its intermediate files it means running all the jobs one step at a time to see where the field gets modified. And THEN you have to open the program and find out what it's doing and why.

      It's not all that different from any other system that has data which is shared between various components, but somehow solving the problem using TSO makes it all seem so primitive.

      (XEDIT is one of the best text editors I've ever used, though.)

  3. I wonder... by fuzzyfuzzyfungus · · Score: 3, Funny

    If recruitment would be any easier if the offer included the right to shout "Where is your 'right-sizing' now, bitches?" into the face of the nearest PHB at will, in addition to the fat salary?

    1. Re:I wonder... by John+Hasler · · Score: 5, Funny

      "Sam? Sam, this is Frank, CIO back at Engulf and Devour. How is the transition away from the mainframe going? Well, listen. That's what I'm calling about. Yes, yes, I know you're retired, but the cloud isn't working out quite as we'd planned, what with the economy and all, and the kids are having a bit of trouble keeping ol' Betsy going. Yes, I did read that memo you wrote, and it turns out you had some good points. Listen, would you be up for a bit of consulting? Say, $100/hr, 100 hours minimum? Oh. That much? And a car and driver? Well, I'm afraid my budget won't quite stretch that far...No! Please don't hang up! Let me talk to the CEO and get back to you, ok? Please?"

      --
      Warning: this article may contain humor, sarcasm, parody, and perhaps even irony. Read at your own risk.
  4. Re:Here is to.... by 1c3mAn · · Score: 5, Insightful

    The Mainframe does it job and does it well. Nothing comes close in Data Throughput Processing with the amount of reliability that a mainframe brings.

    Computer 'Experts' have been saying that the mainframe is dead since the early 90s, but here we are 20 years later and I still have a job programming for it, and I don't see it going away anytime soon. Small to mid-level servers just don't have the capacity to deal with the growing about of data generated. Fedex does in the neighborhood of 2 billion transactions a day, you cant just wipe together a Beowulf Cluster and think it will do the job reliably.

    Or the better question is. How much do you trust the Federal Reserve to run all its processing on Windows machines. Or Wall Street. Ever consider if a transaction there is 'lost' because a windows blue screen? Even linux machines arent as dependable as a Mainframe. The IBM Z boxes actually have their own redundant parts included in them already. Not to mention that it will phone in its own tech support request.

    Mainframes are not for everyone, but they do fulfill their job well when you do need them.

    There are also enough tools out there like SOA so that even Java "Kids" can write applications for them easily.

    Mainframes run the world.

  5. Re:Here is to.... by sexconker · · Score: 4, Insightful

    Uh, why?

    Mainframes are fucking rock solid, reliable pieces of equipment.

    They do the damned job like nobody's business.
    The only issue with mainframes is that we haven't kept the people along with the software we chose to run on them decades ago.

  6. Oblig. Ref. by dugrrr · · Score: 4, Funny

    from BSG: "Any return to COBOL will exact a price paid in blood."

  7. The modern mainframe - Who cares about COBOL? by Ken+Hall · · Score: 5, Interesting

    I went from UNIX in the late 1970's to mainframe zOS (MVS/OS) to VM and Linux on the mainframe. Anything you can do on an Intel box (or a room full of them), you can do on a mainframe, cheaper and more reliably, once you get past the first big financial hit. I've seen the so-called cost studies that supposedly show the room full of Intel white boxes are cheaper. Once you factor in the "unseen" costs, like the article says, and get past the startup, the mainframe looks VERY good.

    Current mainframes aren't what people remember from the past. They're (physically) small, agile, and well suited to certain workloads (can you do 256 concurrent DMA transfers on an Intel box?). The problem is, the only companies that seem to be able to justify them for new workloads are ones that already have them for legacy work. IBM hasn't shown much interest in the low-end of the market (sell small boxen, then discontinue them, push licensed emulation, then kill it, etc).

    Our biggest problem is finding people who know the technologies. I give classes to our Linux SA's on this, and they're usually surprised at what the current zSeries boxes can do.

    Don't misunderstand, there are plenty of applications where Intel boxes make sense, I work both sides of the fence. I just hate to see mainframes maligned as "obsolete" by people who don't understand what they are now.

  8. Re:Here is to.... by tonyr60 · · Score: 3, Informative

    I have been tracking worldwide server revenues for a few years.  Over the past 2-3 years the market share between Mainframe, UNIX, Linux and Windows has been very flat: Windows 40%, Unix 35% Linux 14%, mainframe (ZOS) 11% (IDC Worldwide Server Revenue marketshare).

    Quarter    Windows    Linux    UNIX    ZOS
    02/06    34.20%    12.60%    35.00%
    03/06    34.40%    12.40%    34.20%    11.30%
    04/06    34.90%    11.40%    33.50%    11.40%
    01/07    38.80%    17.00%    35.00%
    02/07    38.20%    13.60%    31.70%    9.50%
    03/07    40.40%    13.40%    31.10%
    04/07    36.60%    12.70%    33.20%
    01/08    39.20%    13.70%    30.60%    8.40%
    02/08    36.50%    13.40%    32.70%    11.80%
    03/08    40.80%    14.00%    29.70%    9.40%
    04/08    35.30%    13.60%    36.20%
    01/09    37.30%    13.80%    33.10%    9.00%

    ZOS is not always reported in press releases and I don't purchase the IDC report.

    Looks like neither Mainframe or UNIX is dying, or that Linux is dominating.

  9. Bad bean counting by Hoi+Polloi · · Score: 3, Interesting

    ...If you do a total cost of ownership, the mainframe comes out cheaper, but since the costs of a mainframe are immediately obvious, it is hard to get it past the bean-counters of an organization.

    I've found this to be true of many aspects of IT, not just concerning mainframes. I've watched customers struggle to get decent performance and constantly hit limitations with a certain database product (not Oracle) because it was virtually free and they didn't want to spend the capital cost on an Oracle license. The total man hours spent, time lost, etc on getting their "free" db up to speed vastly exceeded the cost of the Oracle licenses and they still have problems with it.

    --
    It is by the juice of the coffee bean that thoughts acquire speed, the teeth acquire stains. The stains become a warning
  10. Re:Here is to.... by AvitarX · · Score: 4, Insightful

    But I bet google loses lots of data. They certainly have had massive amounts of down time (by main frame standards).

    search from 2 places, different results. They don't have highly critical data, so they can sloppily store and syncronize as needed. A liberty that Fedex does not.

    --
    Wow, sent an e-mail as suggested when clicking on "use classic" banner, and got a fast response that addressed my msg
  11. huh. from what I have seen, by LukeCrawford · · Score: 3, Insightful

    Finding people who know how to properly use oracle is a real bear. Sure, you can hire people with oracle experience, but most of them were the 'corporate DBA' types who don't know how to do anything out side of the script. I can't tell you how many clients I've seen struggling with their oracle installs; either because the system does not perform as promised, or because the 'cluster' needs to be rebooted every time one node crashes in an unexpected manner.

    Now, I'm just the Linux janitor, not a DBA, but when I see those problems on MySQL or PostgreSQL, I can fix them. I've replaced more than one MSSQL database with a MySQL setup, and often see orders of magnitude speed increases that I suspect are due to misconfiguration of the proprietary database. The open-source stuff is just plain easier to use, at least for Linux janitors like me, and has better support.

    I'm sure Oracle and MSSQL are both fine databases if you know how to use it and you configure it correctly; I'm just saying that paying a lot of money doesn't relieve you from needing to know those things. You still need to pay for a technician who actually understands it. The advantage of the free (as in freedom) products is that there are a whole lot more people with real (that is, non-scripted, where you need to do something new or are expected to solve a problem beyond 'reboot and apply the redo logs') experience with the free databases than with multi-million dollar oracle installs, and that sometimes your expensive support people just shrug and say 'I don't know. why don't you upgrade your linux kernel.'

    Sticking with the free stuff, using a search engine such as google gets you pretty good support for commonly used free software. Often better support than what you get when you pay lots of money for support.