Networking

09:06 AM
Connect Directly
RSS
E-Mail
50%
50%

Mainframe Brain Drain Raises Serious Concern

As IT pros with deep mainframe know-how approach retirement age, a major skills gap may await enterprise CIOs that still rely on the decades-old technology.

Image credit: Sam Beebe on Flickr.
Image credit: Sam Beebe on Flickr.

Comment  | 
Print  | 
Comments
Newest First  |  Oldest First  |  Threaded View
Page 1 / 4   >   >>
Bigfoot54
50%
50%
Bigfoot54,
User Rank: Apprentice
4/1/2014 | 3:46:09 PM
Another Problem
The other problem facing the mainframe world as well as the rest of the IT world is that ubiquitious onager known as a personnel recuiter.  Many of these people are the same people that were unable to cut it in a Computer Science or an Information Systems program in college.  They do however seem to have learned enough IT buzz words before changing their major to history or philosophy to obtain employment as a recuiter, as such positioning themselves to be a oozing carbuncle on the posterior of those who could make it in a CS or IS program.  These recuiters fail to realize that COBOL is pretty much COBOL regardless of platform.  Although I had four courses in COBOL in college, did COBOl exclusively  for about 6 years, I can not now get a job in an IBM COBOL environment because I have never had the opportunity to learn CICS.   Having survived courses in Assembler and Mainframe operating systems, I can't imagine that learning CICS could be any more difficult than either of those two courses.  Yet recuiters will not even present me to a potential emoployer for this reason.  I think that what is needed is a law similar to the real estate law that requires that any offer to buy be presented to the seller, which requires that if a candidate can demonstrate training or experience in the primary skillset specified on a job ad,  that the recuiter be required by law to present the candidates resume to the hiring managers for consideration.  Too many well trained highly experienced people are out of work because some ignoramus in a recuiting firm is looking for cookie cutter candidates.  

The other problem is corporate personnel departments who frequently write position requirements without any direct knowledge of what the technical requirements entail and are incapable of understanding that a candidate who does not have A,B,C,and D on their resume but does have A, B, D and E could function in a given position as well as candidates having A, B, C, and D.  Hiring managers need to wake up.  Their problems as stated in this article are in large measure of their own creation, due to their incompetence and their own lack of professional experience in the technologies that they presume to manage.
BetsyJ958
50%
50%
BetsyJ958,
User Rank: Apprentice
3/24/2014 | 6:34:09 AM
Please open your eyes
The author clearly isn't looking beyond the edge of his desk.   As one of the 'old-timers' I have been involved with IBM mainframes for 30 years and I have watched the platform continue to grow and embrace any new technology you want to throw at it.  I have made certain that I keep my skills updated as well.   Any of the dinosaurs you mention are more ostriches with their heads in the sand.  Every discipline will have people who just maintain the status quo but to lump everyone together is an insult.  Also, the author obviously isn't aware of the growing number of new mainframe professionals being groomed, Marist College comes to mind first.   I have to shake my head at the narrow focus of people like the author - just as I do at the people who think virtualization is new....what do you think the mainframe has been doing for 50 years? 
eairey039
50%
50%
eairey039,
User Rank: Apprentice
3/19/2014 | 1:29:23 PM
Bridging the Skills Gap
The current IT skills gap is a growing concern. As discussed in the article, young professionals are entering the workforce simply lacking the traditional skills possessed by experienced mainframe pros reaching retirement. There are two issues you mention in the article that I believe we can help address as an industry -- One, the perception of mainframe and COBOL skills and Two, the lack of education and training opportunities offered to young professionals. As you state, mainframes aren't perceived as 'cool' these days, nor is COBOL coding. However, mainframe systems and COBOL applications are still very critical in supporting the business organization. Did you know that COBOL still powers 70% of all business transaction processing systems, and there are more than COBOL transactions processed every day than Google and YouTube web searches combined!  Many of our 'every-day' activities interact with a Mainframe or COBOL system, oftentimes without us being consciously aware.  Given our dependency on this technology, and the apparent talent gap, who will support these legacy applications?

In order to bridge the gap, academic institutions and organizations must work together to prepare the next generation of workers with the skills necessary to succeed in today's workplace. According to recent research findings from Micro Focus, 85% percent of respondents confirm it's difficult to find staff or new recruits with mainframe application skills. Not only that, but 14% of staff members currently responsible for this task will retire in the next 5 years — up from 11% in 2012. The study also found that the majority of IT leaders (83%) believe it's valuable for students to learn mainframe programming languages and more than 9 out of 10 say these languages should be taught as part of the standard IT curriculum. The reality is that only 27% of universities around the globe adhere to these standards. In order to fill the gap we must teach next generation IT pros the legacy skills necessary to maintain and enhance today's critical business systems.

The current skills gap has actually opened tremendous opportunities for the next generation of IT professionals. For those entering the industry, it is to your advantage that you learn these legacy skills in order to both maintain these mission-critical business systems but also to position yourself for a lasting and rewarding career!

-Ed Airey, Product Marketing Director of COBOL, Micro Focus
GerhardA320
50%
50%
GerhardA320,
User Rank: Apprentice
3/19/2014 | 8:17:30 AM
Why pick on the mainframe?
One attitude that seems to be prevalent in such discussions is that implicit assumption that somehow the mainframe is deficient as a technology.  Yet, what is this supposed deficiency? 


So the argument invariably shifts to cost, without actually demonstrating why alternate technologies should be cheaper [which they aren't] or how they are more flexible [which they aren't].

Instead we continuously see a picture being painted of the mainframe being some old technology as if it were still some huge beast filled with vacuum tubes.


I'm always fascinated by how someone may bring up the historical image of a mainframe taking up a whole room.  Invariably they don't know what to say when I point out that this is precisely what they are now so proud of when they point to something like the Google data centers.  Yes, we've come full circle.
GerhardA320
50%
50%
GerhardA320,
User Rank: Apprentice
3/19/2014 | 8:06:49 AM
Re: MF talent
While your observation that many old-timers have not kept up with newer technologies, there are also a fair number that have and are quite diversified.  However, the reverse cannot be said.  The younger "talent" knows virtually nothing about mainframes and the institutions responsible for their education are even more ignorant.

So, it's always interesting that mainframers get accused of being "stuck" in their technologies, while no one ever suggests that Windows or Linux folks learn the mainframe.
moarsauce123
50%
50%
moarsauce123,
User Rank: Apprentice
3/19/2014 | 7:59:34 AM
Good luck getting the genie back into the bottle
The industry can only blame itself for telling everyone that mainframes are dead. Quite contrary, the mainframe model is alive and well even when it is called "cloud".
anon2655720611
50%
50%
anon2655720611,
User Rank: Apprentice
3/19/2014 | 7:26:01 AM
Re: MF talent
Who said you are the only one learning other skills, besides the MF?  Did I say that people are refusing to learn other things, and thus being let go?  
Brian.Dean
50%
50%
Brian.Dean,
User Rank: Ninja
3/19/2014 | 3:46:22 AM
Re: Just do like my company is doing...
I get a similar view from financial institutions, provided with the right API it is possible to move from a mainframe but it's a slow process. These API requires developer skills from both worlds and the firms that have embarked on a long term plan will manage to move onto a modern system that does not have a skills shortage.
anon6985051470
50%
50%
anon6985051470,
User Rank: Apprentice
3/18/2014 | 11:08:50 PM
Re: MF talent
As I was reading this article, I was already saying to myself, "The comments will be full of folks whingeing about there being plenty of mainframers who can't find jobs", and I was right.

The ignorance cuts both ways: too many mainframers haven't learned anything since 1981. They haven't figured out how to use Google, refuse to look at Linux, think TCP/IP is something newfangled that they don't need to pay attention to.

This isn't 1980: the mainframe is just one component in the IT infrastructure, and whether it's better for a given use case or not, it doesn't stand alone. Learn something new. Embrace new technologies. Make yourself more valuable. When it comes time to cut someone, who do you think they're going to pick: the cranky old fogey who refuses to move forward, or the cutting-edge kid who's up on the latest whiz-bang stuff?

Paradoxically, the fact that the mainframe keeps running and running doesn't actually help here: it's all too easy to conclude that something that never causes a crisis must not be very difficult to use, or perhaps not even that useful. That isn't an argument for destabilizing the z environment, mind you! But when there's a networking problem involving an x86-based web front-end interacting with middleware and winding up in DB2 on z/OS, it would behoove the z folks to be part of that solution, able to understand at least some of the other technologiies involved, and not just say "Nope, DB2 is fine, your problem, <click>".

I've been using mainframes since 1975 or so, and that's my primary job still. But along the way, I've become familiar with Windows, Linux, networking, and a host of other technologies, because they make me better able to do my job. My skills in those other areas certainly aren't at the level of my z skills, but they're strong enough that when someone starts talking about a multi-tier application environment, I can understand and contribute.

Yeah, this is politics to some extent. It's also not being a dead shark: the industry keeps moving forward; so should you.
anon2655720611
100%
0%
anon2655720611,
User Rank: Apprentice
3/18/2014 | 8:27:06 PM
MF talent
There are PLENTY of mainframers, not that old, that are beign cut for offshoring.  Tech more than any other field makes excuses about no talent, and requests more offshore people.  It's all about the money, come on people...   
Page 1 / 4   >   >>
Slideshows
Cartoon
Audio Interviews
Archived Audio Interviews
Jeremy Schulman, founder of Schprockits, a network automation startup operating in stealth mode, joins us to explore whether networking professionals all need to learn programming in order to remain employed.
White Papers
Register for Network Computing Newsletters
Current Issue
2014 Private Cloud Survey
2014 Private Cloud Survey
Respondents are on a roll: 53% brought their private clouds from concept to production in less than one year, and 60% ­extend their clouds across multiple datacenters. But expertise is scarce, with 51% saying acquiring skilled employees is a roadblock.
Video
Twitter Feed