Your Mainframe isn’t out of Capacity.
It’s out of Balance.
April 21, 2026
How JOPAZ makes COBOL batch workloads eligible for execution on IBM zIIP, freeing your general-purpose GP without changing code.
80 %
or more batch COBOL CPU savings
Consider this: your batch workloads may be growing, and the General Processor (GP) is regularly running at high utilization during batch windows. Performance is challenged. Leadership is asking about scaling and costs. Someone is starting to float the phrase “modernization project.”
Before you commit to a multi-year, multi-million-dollar project, ask yourself a simpler question: What if your mainframe has enough power, but it’s not distributed correctly?
That’s the premise behind JOPAZ, now available through SDS. It’s a targeted, low-risk solution that offloads COBOL batch workloads from general-purpose GP engines to IBM zIIP™ specialty processors, instantly freeing capacity for the work that matters most.
The capacity problem most shops don’t fully understand
IBM Z systems are equipped with multiple processor types. Your general-purpose GP handles the bulk workloads, including your COBOL applications. But IBM also provides zIIP (z Integrated Information Processors) specialty engines designed for specific workloads, billed at lower software licensing costs.
The challenge? Most COBOL batch jobs run exclusively on the GP by default, even when portions of that work could legally and efficiently run on zIIP. As batch volumes grow and peak utilization climbs, shops find themselves in a frustrating bind: the hardware can handle more, but the CP becomes a bottleneck that caps performance.
What JOPAZ Actually Does
JOPAZ works by compiling your existing COBOL source code into Java bytecode, a format that can execute on the zIIP processor. At runtime, eligible batch jobs run on zIIP instead of the general-purpose GP. Your application logic doesn’t change. Your COBOL source is maintained exactly as it always has been, with the same development tools your team already knows.
How it works
- Identify High-Utilization Batch Jobs – Work with SDS on the JOPAZ team to pinpoint which COBOL batch workloads are consuming the most GP cycles; these are your highest-opportunity candidates to offload to the zIIP.
- Compile to Java Bytecode – JOPAZ compiles your COBOL source into Java bytecode. No changes to application logic, data structures, or business rules. Your code doesn’t change.
- Execute on zIIP at Runtime – Eligible workloads run on the zIIP specialty engine. GP utilization drops. You gain capacity right away.
Why No Code Changes is a Game Changer
If you’ve been in mainframe operations for more than a few years, you’ve lived through at least one “migration project.” You know what it means when someone says, “We’ll just need to refactor a few things.” Months become years. Scope expands. Business logic that’s been accumulating for decades becomes a minefield for newer employees to navigate.
JOPAZ‘s core promise, no changes to your COBOL source code, is a fundamental risk mitigation argument. Your application continues to behave exactly as designed. Your team maintains it with familiar tools. Your databases and core systesms on IBM Z. The only thing that changes is which processor handles the execution.
That’s how JOPAZ is able to provide Proof of Value right away.
Three ways JOPAZ changes what’s possible
- Immediate Breathing Room – Once you begin to redistribute workloads to zIIP, GP utilization drops, often dramatically. That additional capacity is immediately available for new workloads, expanded batch windows, or simply more reliable performance during peak processing. Now waiting. No phased cutover. The rsults how in your first production runs.
- A Foundation for Innovation – AI inferencing on IBM Z, expanded analytics, and new customer-facing applications – these projects often stall not because the idea is wrong, but because there’s no CP capacity to run them. When JOPAZ clears that bottleneck, it doesn’t just solve today’s performance problem. It creates the on-ramp for next-generation workloads on the platform.
- A Smarter Conversation with Leadership -When the capacity conversation comes up in the boardroom, “we’re exploring a zIIP optimization strategy” lands very differently than “we need to migrate our COBOL.” One is a targeted, low-risk efficiency project with measurable ROI. The other is a bet-the-business proposition. JOPAZ gives you the first option.
The Proof-of-Value engagement
One of the strongest aspects of evaluating JOPAZ is the proof-of-value (PoV) engagement. Rather than asking you to take the business case on faith, the process is structured around demonstrating actual savings in your environment before you commit.
In the PoV process, we select a handful of your highest-utilization BOBOL batch jobs, run them, and measure CP savings with and without JOPAZ. You see your numbers in your environment before making a purchase decision. That’s the kind of confidence that turns a skeptical perations director into an internal champion.
Is JOPAZ Right for your Shop?
JOPAZ is most impactful where:
GP utilization is regularly about 70-80% during batch windows. COBOL batch jobs represent a significant portion of your peak processing load. The cost and risk of BOBOL rewriting or full migration are prohibitive. You have zIIP processors available (or are considering them). You need to expand capacity while containing costs.
If any of those describe your situation, a conversation is worth having. A technical consultation with SDS costs you nothing, and the Proof of Value is based on your real data.
Are you ready to reclaim your GP capacity? Schedule a demo with SDS today.
Free Demo/Trial
We offer individualized product demonstrations by request. Your organization can also try SDS Software on your system for 30 days, free of charge.
Phone: (800) 443-6183
Phone: (763) 571-9000
200 Village Center Drive, Suite 250
North Oaks, MN 55127
USA
