Mainframe Modernization: A Practical Conversation with BMC on Understanding Before Converting

I had a blast chatting with Anthony Anter, DevOps Evangelist at BMC Software on The Ravit Show and this one goes deep into a topic many enterprises are struggling with quietly. Mainframe modernization. Not tools. Not hype. Real ground reality.

We started with a simple but uncomfortable truth Tony writes about

Before you even think about converting code, explain what you already have.

That single line sets the tone for the entire conversation.

- We talked about why so many COBOL to Java projects fail even before they begin.

- Why teams rush into conversion without understanding decades of business logic buried in code.

- And why mainframe systems often look like a long game of telephone, where intent is lost but code survives.

A big part of the discussion focused on generative AI.

Not as a magic converter, but as a way to explain, map, and document existing systems before touching a single line of Java.

When teams finally see dependencies and flows clearly, the surprises are often eye opening.

We also broke down a critical distinction that is often ignored

Code explanation is not the same as code translation.

Missing this is where most modernization programs go wrong.

Tony also shared why refactoring before rewriting matters, what practical cleanup really looks like, and how GenAI can help create Java code that is actually maintainable, not just converted.

One part I personally found valuable was the balance between automation and human expertise.

Where AI helps, where humans are still irreplaceable, and what governance is needed so AI output can be trusted.

We wrapped with Tony’s checklist for smarter modernization and one clear takeaway for anyone working on or around mainframes today.

If you are a CIO, architect, or mainframe professional thinking about modernization, this conversation will save you from expensive mistakes.

#data #ai #mainframes #bmc #theravitshow