Dear fellow mainframer,
This week, we’re kicking off the planning for the Mighty Mainframe Conference. It’s always a bit of a challenge to map out how all the great speakers and topics could fit into the available time. We want to strike the right balance between covering the big-picture themes of modernization and giving enough space to the practical details that shape real projects.
And of course, the schedule is only part of the story. Don’t just listen to the sessions-ask the speakers the questions that matter to you and spark conversations with other participants. The conference provides the framework, but the real value often comes from those in‑between moments: chatting on the terrace over coffee or walking lungo mare along the Adriatic while discussing how AI can help modernization.
Why We Need to Reinvent Mainframe Modernization
Mainframe modernization has turned into a buzzword—used so often and in so many different ways that it’s started to lose its meaning. Too many discussions stay locked on specific legacy technologies like IMS or COBOL, drifting into something that feels more like an archeology debate than a conversation about where systems need to go next.
We want to shift that perspective. Modernization shouldn’t just be about upgrading old components. It should be about building future‑ready infrastructure, while still taking full advantage of the applications and data that have served organizations well for decades.
That’s why Armin Kramer, Head of Mainframe at CROZ, introduced the idea of “15 (+1) ways to reinvent mainframe modernization.” It’s a practical spectrum of modernization approaches, all moving in one clear direction. You can read the full story here.
COBOL for Gen Z
Modern COBOL development is really about delivery discipline on Z: making every change easy to trace, every build repeatable, every test automatic, and every deployment predictable. When you put Git-based reviews in front of changes, use dependency-aware builds with DBB, and run a pipeline through Jenkins with Zowe handling the “talking to z/OS” part, COBOL stops feeling fragile and starts feeling like a platform you can ship from with confidence.
My colleague Armin Kramer captured this nicely in a step‑by‑step walkthrough, showing how IDz and VS Code can coexist for different kinds of work, how CobolCheck brings real regression safety to business logic, and how Wazi Deploy makes promotions consistent instead of ritualistic.
Beyond the technology and organizational benefits, modernizing the COBOL development experience also closes the generational gap. Instead of a culture shock when Gen Z developers open ISPF and other green‑screen tools, they feel at home—just like with any other modern development stack.
Industry insights
IBM announced it would discontinue the zPDT program.
The end of zPDT standalone support puts real pressure on mid-tier ISVs. Many rely on zPDT for development and testing because it is affordable and gives them control. The alternatives can raise costs quickly and introduce security and data sovereignty concerns.
Most people I spoke with were shocked by the decision, but Mark Wilson was especially vocal about it—and I think he’s completely right.
IBM needs to recognize the real impact this decision has on ISVs and act quickly to reduce the damage.
Bringing Enterprise AI Platform In-House
IBM z17 with Spyre provides an ideal foundation for building a self‑hosted enterprise AI platform. It enables secure, compliant, and cost‑controlled AI adoption by keeping both models and data within your organization, ensuring digital sovereignty and deep system integration. Bringing AI in‑house offers numerous benefits, especially when it comes to cost.
