Slashdot Mirror
Mainframe Operators Needed
blueforce writes "Computer World is reporting that there's a shortage of skilled mainframe workers on the horizon. Quote: "Getting IT professionals, especially young ones, interested in learning mainframe work isn't easy." No kidding. While I've never worked on a mainframe, I have worked on AS/400's. 3 words - Mind Numb ing. Perhaps it's time for a more long-term solution to the problem. Interesting nonetheless. Who'da thunk it - a shortage in IT. What's next, COBOL?"
The problem is lack of specialized talent. In neither undergraduate nor graduate school (graduated last year) was a single mainframe course offered. The "old timers" who work on mainframes here are their own special group-- very few people are brought in, and certainly it would be a good idea to change this, since mainframes are years ahead of PCs in terms of hardcore OS technology. If colleges didn't focus so strongly on learning VB and Office, maybe CS degrees would mean as much as they used to...
Wer mit Ungeheuern kämpft, mag zusehn, dass er nicht dabei zum Ungeheuer wird. --Nietzsche
I don't entirely understand why mainframe work should be much more mind-numbing than point-and-click or shell-hopping. Would somebody with AS/400 experience explain what makes administration of the machines completely non-automatable, and thus requiring massive amounts of repetitive input?
--Dan
We still run a couple of HP3000s...a 928 and a 918. Before that we had another model, I forget which one. In any case, there is 20+ years of custom in-house COBOL programming invested in those systems. Most of that code is still serving its purpose very well. We have started updating the apps and have done some web development with it, but if it works, why change it? The only reason we have even considered migration is because HP has finally pulled the plug on the 3000 line, not because it couldn't serve its purpose. And hey, who doesn't like a half-obscure OS (MPE/ix) running on a 48MHz machine supporting 200+ users?
Geek used to be a four letter word. Now it's a six-figure one.
The problem is that no one teaches mainframe operations in schools, you basically need to learn by being dropped into it - and not screwing up everything. Fewer and fewer businesses are willing to invest in promising new talent to learn these legacy systems, but their own mainframe gurus are retiring or dying off - so eventually this corporations will 'bleed out' skill-wise.
And no, the mainframe cannot be replaced by a client-server solution. I listened to this moron chant throughout school - mainframes are not dead. REALITY CHECK - there are just some applications where a mainframe makes more sense. Mainframes can handle enormous amounts of data without having to break it up for a cluster, or without being bogged down with I/O like most client-server type solutions. Mainframes are great when you need to handle databases with tons of information in it - and you need to consistantly dig through it. Most machines cannot handle it, and will buckle. Mainframes almost never buckle, unless you are testing new stuff on them (naughty newbie - that's what a test LPAR is for) or you do funky things to them.
Real MCSE's know that real main frames run Windows2000 Server!
Unix is just DOS with funny application names (ga-new what?)
That's only part of the issue. I didn't learn squat about sysadmin tasks in University, because the focus is on teaching you how to think about software development, not how to use a particular tool or platform -- that's what tech schools are for.
A far bigger issue, as was already pointed out, is the mind-numbing tedium of being a mainframe operator. Alas, the same applies to being an operator on any system, as your main job is to swap media for backups, stock the print servers, and act as remote fingers when support staff call in on a page.
Regardless of platform, the only operators I knew who were happy with the job were middle-aged people who were more concerned about job stability than job challenge/fullfillment. Many of them were highly skilled, knew more about the systems than the developers, and would have made good developers. They just didn't want the pressure and insecurity that comes outside the data center.
As to "learning VB and Office", it sounds more like a tech school than a university. I've never heard of VB or Office being considered part of the programming course on a university campus. I have seen it offered as a half-credit course to help out students who have no prior experience with basic office automation tools, but who need the basics in order to be able to prepare and submit their coursework.
Another issue with getting people to consider a career as an operator is that the job stability is a smokescreen. Who wants to take a job for lower pay, that has little or no challenge to it, requires dealing with pissed-off user managers, and is subject to termination whenever someone gets a brain-fart about "saving" by outsourcing?
I do not fail; I succeed at finding out what does not work.
Why do you consider it mindnumbing? I'm 27, and I've been working with AS/400s for about 4 years. They aren't anymore mindnumbing than running an *nix CLI, or point and clicking all day. On a side note, the AS/400 is quite the machine. I could sit and name all the great things it can do that are better and faster than any Intel system, but it'll still be labeled "mindnumbing" because it doesn't play solitaire.
I went to college for this?...
Things too reliable? Predictable? Functional? Secure? Just can't find anything to do?
Windowsize it!
Just ten lines of Windows code will have you scrambling for hours to try and figure out what in the heck has gone wrong!
Add twenty lines of Windows code and you've got a month worth of worries on your hands!
And for the truly daring: A mission-critical Windows application!
Kiss the wife and kids goodbye! You'll never eat/sleep/bathe in peace again!
Windowsize it!
(Not approved for those with heart conditions/risk of stroke/high blood pressure/pregnant)
When you compare MVS to UNIX to Linux, and do the math, MVS wins big. Billions of lines of mainframe investment are not going anywhere soon. Billions were spent on making legacy systems Y2k compliant, now that the investment has been made, companies are finding it difficult to call for a re-write.
IBM saw this coming a while back. The 390 mainframes were renamed Enterprise Server (and we all snickered). However, the enterprise server is now running Linux, Websphere, integration services, websites, ASPs, and the legacy systems with incredible stability.
It is difficult to find operators because in many mainframe shops the job consists of running print jobs and contacting support staff when alerts occur. It is no longer a career. It would improve if companies started treating it like a first step. Hire some college students or entry level employees and provide a career path to greater opportunity. Isn't that what we all want?
Even though a DEC ALPHA running VMS isn't considered a main, we had one running at my job for 7 years. It was the payroll system. They never got rid of it because no one knew what to do with it, it ran for 7 years with nary a reboot, and it just worked. Then they go a spend $2 million on Siebel and it was slower than molasses. Because of that, they had to dump 500 employees. Siebel is gone, but that DEC Alpha is still churning away.
If you're not a Liberal in your 20's, then you have no heart.If you're still a Liberal in your 30's you have no brain.
- Run some java apps on it
... there is a full blown Java2 1.4 VM available (what better platform to run a Java VM on but one that implements the concept of VM at it's core) - Run Linux apps -- Suse, Redhat, & TurboLinux (I think) distros available to run in a logical partition
- Run Apache2 web servers
- Run AIX apps on it
This ain't your father's AS400btw: Did you know that when IBM changed the CPU on the AS400 from a 48bit CISC system to a 64bit RISC system (PPC based) there was almost zero application programming changes required
mm
As someone previously said, It's a different world out there. OS/390 is an amazing OS, we had 5 instances of it running at once on the mainframe (2 production and 3 development regions) and then I installed Linux too :-D
Initially I was given a measly 5% CPU for my Linux region....but that's more than enough for Linux to make a mark!
Coming back to the point, the reason for the different world can be summarized in two words - Batch Jobs . So the task of the operators will be to keep staring at the console to look out for requests to load up cartridges (yes, thats the primary backup medium) that a job needs to read stuff off or start some massive printing and computational jobs from time to time. I worked for a large conglomerate, employing more than 30,000 people, so every month the pay-check printing job on huge line printers took about 4 days to complete. Other task included checking DASD usage (mainframe harddrives) to check upcoming shortages , etc.
Even programming for it was fun, I was primarily in charge of the opensystems portion of it, including Domino Go Webserver, O-MVS (unix) and Linux. But I can understand why there is a shortage of manpower. The cool technology does not hit the mainframe world, so you won't get to work on wireless communications, kernel hacking, etc. I am now a Linux systems programmer and I dont wanna go back too, but it was an experience worth getting.
Arrgggh..i have been barfing too long...back to work!
There is no patch for stupidity
Visit my blog