Slashdot Mirror


Mainframe Techies Are A Dying Breed

dipfan writes "Great piece in today's Financial Times on the surprising survival of mainframes - but the problem in the US is finding experienced techies to run them: "55 per cent were over 50, compared with fewer than 10 per cent of those with Unix or Windows NT server skills." Cobol programers, still needed for legacy applications, are mostly in their 40s. Help is on the way, though, thanks to IBM's use of Linux, which "freshens the labor pool" according to the article." (See also this earlier post on the mainframe-operator labor pool.)

10 of 483 comments (clear)

  1. Employers' fault... by darken9999 · · Score: 5, Insightful
    Maybe if employers wouldn't require every employee to have such mass amounts of experience, there would be a few younger admins around. You know, almost like a junior admin... "Well, he knows how to admin a system, so we can teach him the specifics."

    I think being a mainframe admin would be a blast (maybe I just don't know better), but in my eight years of sysadmin work, I've never touched a mainframe. Every job posting I recall coming across required previous experience.

    1. Re:Employers' fault... by Xzzy · · Score: 4, Insightful

      > Every job posting I recall coming across required
      > previous experience.

      Takes a long time, but it will become a self-resolving problem. The existing "old guard" will eventually die out (either literally or via retirement) and create a demand in the market.

      This will either cause companies to lower their standards or discard the old mainframes.

      It would make good business sense to address the problem before it reaches critical mass (ie, so much of the old guard is gone that there's no way to train newbies), but if the Y2K problem was any indication, foresight isn't a prerequisite for running a business.

    2. Re:Employers' fault... by Eskarel · · Score: 4, Insightful
      Well I would agree with the fact that it's the employers fault, but disagree on what it is thay are doing which causes it.

      I would of course agree with the frustration tech workers seeking employment right out of college, and workers in general for that matter. It's hard to get experience when everyone wants it to give you a job, but that's not really the problem when it comes to network and sysadmin positions.

      It's perfectly sensible to require people who run something as complicated as a mainframe, or even network administration, or a half a dozen other things require strong experience. However if these companies want to have people available to work on these systems in the future they also have to provide opportunities for people to gain this experience without having to rely on them for full administration. That is to say companies should be hiring more PFY's so that they can train the next generation of administrators through real life experience.

      Employers don't want to do this of course because it involves having an extra employee, but they would be much better off in the long term if they had people who had real experience.

      Of course an additional problem with this sort of thing is unrealistic pay expectations among tech workers in general. No one is going to hire a PFY for 60,000 a year, but there are still many people on slashdot who believe that 50,000 is a ridiculously low salary for a full time job. So while a lot of it is employers being cheap, it's also somewhat us being unrealistic.

  2. Huh? Stuffing FUD in there or what? by stratjakt · · Score: 5, Insightful

    "55 per cent were over 50, compared with fewer than 10 per cent of those with Unix or Windows NT server skills." Cobol programers, still needed for legacy applications, are mostly in their 40s. Help is on the way, though, thanks to IBM's use of Linux, which "freshens the labor pool" according to the article."


    How does linux freshen the mainframe labor pool, and not the Unix/Windows NT pool?

    Linux ain't System/36 or MPE or any other mainframe OS. And show me one linux app that's written in COBOL. (The language exists, but I've never seen it put to use).

    This is a self correcting problem. A good admin/coder can pick up mainframe stuff when he needs to. All the 50+ year olds are still working the jobs they got when they were 30. When they die off/retire, younger folks will pick it up.

    I mean, hell, I picked up enough about MPE and FORTRAN and COBOL to do my job inside of a week. And I got competent with S/36 and RPG at my last job.

    It aint rocket science. It's like a skilled machinist learning to shoe horses.
    --
    I don't need no instructions to know how to rock!!!!
    1. Re:Huh? Stuffing FUD in there or what? by TopShelf · · Score: 5, Insightful

      This more a symptom of employers concentrating on specific experience more than talented personnel. A fundamental skill that the vast majority of IS professionals have is the ability to LEARN and ADAPT. Unfortunately there's no buzzword that can signify this on a resume, so it gets ignored.

      --
      Stop by my site where I write about ERP systems & more
  3. So, the admins are old. by PhxBlue · · Score: 5, Insightful

    What's the problem, here? If the 50-year-old programmer is the only one who knows jack about mainframes, hire the 50-year-old programmer. Don't whine about not having enough qualified programmers, when what you really want is just-out-of-college programmers that you can bully into working for you at half the salary of someone with real experience.

    --
    !#@%*)anks for hanging up the phone, dear.
  4. We are not dead, we just by Archfeld · · Score: 4, Insightful

    moved into more lucrative positions. Match my current salary and I'll go back to hexdump processing, IMS MTO, CICS batch, MVS/TSO, JES3/2, VM, REXX, DOS/VSE you name it. I've been a mainframe/mid-range support in nearly every environment around, I can even roll a VTAM sub-area :)
    But M$ exchange cluster design and management pays MUCH better.

    --
    errr....umm...*whooosh* *whoosh* Is this thing on ?
  5. "mostly in their 40s" -- oh no! by fmaxwell · · Score: 4, Insightful

    Cobol programers, still needed for legacy applications, are mostly in their 40s.

    Oh no! People in their 40s will only want to remain in the work force for another 20 years or so. What will the companies do then? Train people? Not in the U.S.! All employees must be hired with all needed skills. We wouldn't want to spend money training them because that investment would be wasted when we laid them off and shipped their job over to India.

    Nobody gets upset that most CEOs are in their 50s. No one is concerned that corporate attorneys are usually over 40. You don't see a panic because the average charter boat captain is in his 40s.

    Working in the computer field is like living the movie Logan's Run. Once you are out of your twenties, everyone from management to your fellow tech workers thinks your time is over.

    Or is it simpler than that? Maybe companies realize that they can underpay and overwork young, naive, single people but that people in their 40's with experience, families, and responsibilities will expect fair pay, benefits, and working conditions.

  6. Re:Legacy by BitwizeGHC · · Score: 4, Insightful

    Bjarne Stroustrup has been known to observe that the primary difference between "legacy" systems and the systems replacing them is that the legacy system works and scales.

    A case can be built for the verity of that assertion as applied to the mainframe situation.

    --
    N4st0r, trixx0r h0bb1tz0rz! Th3y st0l3 0ur pr3c10uzz!
  7. Locomotives are still around by Ra5pu7in · · Score: 5, Insightful

    Locomotives / freight trains are still used regularly. They serve a need that cannot be met with automobiles or even 18-wheelers. For Joe Sixpack and his family, an automobile is definitely a more efficient way to cross the country. For ABC Florist who relies on fresh cuttings, locomotives take too long - trucks are better. But for XYZ Furniture ordering fifty sofas, twenty-five coffee tables, one thousand various lamps, etc., it would take a large number of trucks (each having a driver to pay) vs. twelve cars in a freight train (one driver to pay).

    There is a use for mainframes in particular industries - personal computers and servers aren't the be-all end-all answer to every computing need.

    --
    I was taking one day at a time, but then several days got together and ambushed me. (from a Rhymes with Orange comic)