There’s still a place for good old-fashioned mainframe training

mainframe

I make no secret of the fact that I think the modern mainframe offers an excellent enterprise technology platform. But there are issues—in particular, that mainframe people (and technologies) speak a language all of their own and management is frightened of losing key people (or of losing control of what these people are doing). At one stage, even I had quite a secure job because I knew what things like IEBUPDTE did and could use it for things other people might waste time programming—few others, apparently, could read the IBM manuals.

So, Knowledge Transfer is part of actually exploiting the wonderful mainframe—and tools like CA Mainframe Chorus are an important part of this. And, of course, a special aspect of this issue (particularly in the mainframe area) is the need to transfer knowledge of legacy applications (and their business context) from retiring employees. See, for example, a usefully hard-headed exploration of this issue by David DeLong (a research fellow at the Massachusetts Institute of Technology’s Age Lab) here.

However, there’s still a place for good old-fashioned training, preferably in an interactive F2F scenario (which helps you learn not only WHAT to do, but WHY; and even WHEN there are special cases and exceptions).

Big mainframe companies like CA Technologies and IBM have always provided mainframe-oriented training and I’ve been very impressed by the students I’ve met at, for example, CA Technologies “mainframe university” in Eastern Europe.

Now, CA Technologies has gone a bit further and created an external training program, available to young IT talent outside of CA Technologies, based on its existing internal one. And, just to prove it’s serious, it’s offering $1M in scholarships for these external students.

If this helps to develop a pool of mainframe expertise independent of any particular vendor, that bodes well for the increased acceptance of the mainframe, especially (I suspect) in emerging economies. Just remember to call it an “Enterprise Server” before the term “mainframe” frightens the horses.

Scholarships will be granted after an evaluation process (using an expert panel which includes representation from the SHARE board of directors), which will look at a candidate’s academic achievements, creativity and technology vision.

Presumably, candidates will have achieved a prior knowledge of general IT before starting as this is only an 8-week, vendor-agnostic program presenting both real-world and project-based learning—when I was picked up off the streets to become a mainframe DBA many years ago, the Australian Dept. Health put me through a fairly testing 1 year post-grad. sandwich course in Comp. Sci. with practical mainframe training in the vacations.

Still, 8 weeks should be plenty of time for someone with general IT expertise to pick up the specialist aspects of mainframe operations and management. Since I believe that the latest mainframes are a valuable technology resource and that much serious business still runs on legacy mainframe systems, I think that this initiative is a good omen for the future efficiency of enterprise IT.

SHARETweet about this on TwitterShare on LinkedInShare on FacebookShare on Google+Pin on PinterestDigg thisShare on RedditShare on TumblrShare on StumbleUponEmail this to someone

David Norfolk is Practice Leader Development and Governance (Development/Governance) at Bloor Research. David first became interested in computers and programming quality in the 1970s, working in the Research School of Chemistry at the Australian National University. Here he discovered that computers could deliver misleading answers, even when programmed by very clever people, and was taught to program in FORTRAN. His ongoing interest in all things related to development has culminated in his joining Bloor in 2007 and taking on the development brief. Development here refers especially to automated systems development. This covers technology including acronym-driven tools such as: Application Lifecycle Management (ALM), Integrated Development Environments (IDE), Model Driven Architecture (MDA), automated data analysis tools and metadata repositories, requirements modelling tools and so on.

  • David, just wanted to add a short anecdote.

    I recently visited a large mainframe client when I met an old acquintance. He introduced me to his successor, an experienced Unix person. The mentoring process had been going on for 12 months already and the “student” told me he now felt reasonably comfortable when he was left on his own for 1-2 days.

    He was flabbergasted by the amount of knowledge that the experienced mainframer had and told me it would take him at least another 12 months to be fully comfortable. If he would have had the possibility of an 8 week full MF training like CA Technologies offers now, he told me it would have saved him 6-8 months.

    I am not saying Mainframes are complex. I am just saying that transferring 30 years of knowledge alone already takes so much time. Learning the basics in 8 weeks should be looked at as the first time (and MONEY) saver…

  • David, just wanted to add a short anecdote.

    I recently visited a large mainframe client when I met an old acquintance. He introduced me to his successor, an experienced Unix person. The mentoring process had been going on for 12 months already and the “student” told me he now felt reasonably comfortable when he was left on his own for 1-2 days.

    He was flabbergasted by the amount of knowledge that the experienced mainframer had and told me it would take him at least another 12 months to be fully comfortable. If he would have had the possibility of an 8 week full MF training like CA Technologies offers now, he told me it would have saved him 6-8 months.

    I am not saying Mainframes are complex. I am just saying that transferring 30 years of knowledge alone already takes so much time. Learning the basics in 8 weeks should be looked at as the first time (and MONEY) saver…www.ca.com/mainframe