Mainframe Blog

What Will Your Mainframe Sysprog Legacy Be?

4 minute read
Kelly Vogt

If you google the word legacy, a mere noun since time began, you’ll find it now has an additional part of speech, an adjective with this definition: “denoting software or hardware that has been superseded but is difficult to replace because of its wide use.”

Ho! Someone was very clever there at Google, but only clever enough to memorialize the pejorative mainframers have suffered for nearly two decades. I recall the standard response when disparaged thus was something like, “Oh, yeah, legacy: a system that works.” And we smugly went about our business, assured we had righteously trounced the impertinent offender.

However, scoffing at naysayers never solved the actual problem of misinformation around the mainframe, which persists today despite the platform being the most modern system of record available to large organizations that require a highly available, reliable and secure environment through which to run their mission-critical enterprise applications and data.

The True Legacy of the Mainframe

Having had our laugh, mainframers must now focus on promoting and justifying the real meanings of the word legacy:

  • Something of value left to someone
  • A thing handed down by a predecessor

I especially like some of the synonyms for these definitions when referring to something of value, particularly:

  • Heritage
  • Endowment
  • Gift

These synonyms really make me think about the mainframe as more than just a platform and instead as an ecosystem of continuously evolving value, experiencing a massive positive transformation to its culture, processes and tools. All of which will soon be left to a new generation of stewards with new talents and ideas. That’s why these synonyms also make me think of my career as a mainframe sysprog and manager.

What Will Your Legacy Be?

I’ve observed there are two sorts of people on final approach in their careers:

  1. The kind who are watching the clock, coasting out, doing “good enough for government” work; for these, retirement cannot come soon enough.
  2. The kind who still have fire in their bellies, are still trying to top their personal best, are still fascinated with the technology, are wanting to start something new and want to see if they can make the latest elephant dance.

The second group of people are the blessed who have found something they love and have hardly worked a day in their lives because of it. Many, if not most, started their careers this way, I believe, but somehow lost the gift. And who can blame them with all the shenanigans that some businesses have foisted upon “their most valuable resources”?

But does any mainframer really want to go out like the first group of people: apathetic, discontent and perhaps bitter? I doubt it. I know I don’t.

How do you want to be remembered? What do you want to see when you look back on your career? What about those you leave behind? In the remaining time you will work, what about your goals and aspirations? Don’t let your career as a mainframe sysprog become simply a job.

This business we’re in, it has literally advanced humankind and drives us, as a people, into the future. We who work with it all share a common fascination for the technology, and we revel in how we take part in that advancement. In so doing, it makes us part of something larger than ourselves.

In my case, I’m proud of my participation and my contribution to this advancement. And I want to hand down a heritage to those who come behind me. It’s incumbent on us older mainframe sysprogs to endow our successors with all we can to help them carry forward.

What we do now, or don’t do, will have consequences for the future. I for one, don’t want any lack of action or failure on my part, to have any negative repercussions. And I surely don’t want my legacy to be described with any words like aftermath, another synonym attached to “legacy.”

As I approach my career end, I think a lot about those taking up the mantle I will lay down. How can I help future mainframe sysprogs succeed? One way would be to automate the seemingly last bastion of manual operation: JES2, where IBM provides a strong spooling facility, but leaves it to the customer’s brain trust to exploit as well as they can.

Leaving a Proper Mainframe Sysprog Legacy

In the main, our successors don’t have the fundamentals most of us have. They may never experience a wait state during an IPL. They may not have learned assembler. Their role begins in the second act.

Fortunately, IBM has done a good job making the base stable. So, the new mainframe sysprogs can jump into the middle of the technology and be successful. But there is plenty we can do to help further position them for success.

Automation is a big one, particularly automated batch processing. Our beloved spoolers JES2 and JES3[1] are real workhorses, but they are still, at the end of the day, manually operated systems. Somebody must configure them, evolve strategies for their best use as needed and monitor and manage them continuously, especially during your peak batch processing windows. Why batch has not been automated by IBM is a mystery.

But there is good news. Compuware ThruPut Manager takes this challenge head-on and solves the problem, endowing the complete automation of the batch workload upon the harried operations area. Our rules-based, policy-driven control system automatically manages all facets of batch processing, from job entry through execution.

Using our rules-based, Job Action Language (JAL), shop standards are easily enforced. And the supporting code can be quickly adapted to meet the installation’s changing needs. No more inertia, passing up opportunities to evolve and improve because it is too difficult to write or modify static system exits. Compuware has brought agility to batch management.

Our policy-driven components replace manual initiator management, negating the need for continuous operator attention, monitoring and manipulation of initiators and job classes. Batch just runs, with constancy and predictability. This frees operators from these mundane tasks and allows them to focus on serving customer needs such as exception handling, demand processing and one-off requests.

I’ve worked with ThruPut Manager for over 20 years as a mainframe sysprog up to the operations director level. At a previous employer, we went from out-of-control to full control, from piecework to assembly line, from clunky to streamlined, from react to proact with this tool. We no longer simply had only the responsibility for batch, but we had the means to manage and control it as well.

When you step down as a sysprog, how will be remembered? There is no better heritage to bequeath, no finer gift to give to future mainframe sysprogs, than automation of your batch workload.

[1] ThruPut Manger does not operate in a JES3 environment, but it can process JES3 JCL on JES2.

These postings are my own and do not necessarily represent BMC's position, strategies, or opinion.

See an error or have a suggestion? Please let us know by emailing

BMC Bring the A-Game

From core to cloud to edge, BMC delivers the software and services that enable nearly 10,000 global customers, including 84% of the Forbes Global 100, to thrive in their ongoing evolution to an Autonomous Digital Enterprise.
Learn more about BMC ›

About the author

Kelly Vogt

Kelly has over 40 years of z/OS systems programming, performance tuning, capacity planning, operations and management experience. Prior to coming to work for BMC Compuware, he managed an evolving batch strategy for a major insurer, improving batch services for his customers, while reducing operating costs and risks by fully automating batch processing.