But these approaches are fraught with risk. They often involve unpredictable costs, long implementation timelines, and lost functionality when the new system can\u2019t replicate the decades of business logic baked into the original COBOL code. And, they\u2019re often all-or-nothing solutions, meaning that when modernization hits a roadblock, it\u2019s often too late to reconsider.<\/p>\n\n\n\n
A New Way: Reclaiming GP Capacity with JOPAZ<\/h3>\n\n\n\n
JOPAZ offers a non-disruptive alternative. Instead of moving off the mainframe, JOPAZ keeps you on the platform while significantly reducing the load on your general processors. It does this by making COBOL batch workloads eligible for execution on IBM zIIP engines.<\/p>\n\n\n\n
With workloads executing on zIIP, organizations can instantly free up GP capacity for other high-priority tasks.<\/p>\n\n\n\n
How JOPAZ Works: Under the Hood<\/h3>\n\n\n\n
The transition from a standard batch COBOL workload to a zIIP-eligible workload happens in four phases:<\/p>\n\n\n\n
- \n
- Identification: Identify batch jobs that are consuming the most GP resources.<\/li>\n\n\n\n
- Compilation: JOPAZ takes your existing COBOL source code and compiles it directly into Java bytecode.<\/li>\n\n\n\n
- Execution: This bytecode runs on a Java Virtual Machine (JVM), making the workload eligible for the zIIP engine.<\/li>\n\n\n\n
- Scale: Repeat with as many or few batch jobs as needed. JOPAZ is a phased approach to workload optimization, keeping your business running as usual.<\/li>\n<\/ol>\n\n\n\n
Critically, no change to the COBOL code is required. Your business logic remains intact, and your developers continue to work in the environment they know.<\/p>\n\n\n\n
Real-World Results<\/h3>\n\n\n\n
Case Study 1: Retail Energy Provider<\/strong><\/h4>\n\n\n\n
This organization was struggling with heavy DB2 workloads. They implemented JOPAZ to see how effectively it could handle database-heavy batch processes.<\/p>\n\n\n\n
- \n
- With a Single zIIP Engine:<\/strong> They achieved a 76% reduction in batch C<\/strong>OBOL CPU usage on the GP.<\/li>\n\n\n\n
- With Two zIIP Engines:<\/strong> After seeing the initial success, they added a second zIIP engine. The CPU savings jumped to 92.9%.<\/li>\n\n\n\n
- The Impact:<\/strong> Even with heavy SQL calls, JOPAZ was able to leverage the zIIP engine not just for the executable itself, but for the associated DB2 SQL processing.<\/li>\n<\/ul>\n\n\n\n
Case Study 2: North American Member-Service Organization<\/strong><\/h4>\n\n\n\n
For this large automotive and financial services provider, containing costs was a top priority. They ran two batch streams in sequence to test JOPAZ’s efficiency.<\/p>\n\n\n\n
- \n
- The Result:<\/strong> An impressive 94.84% reduction in batch COBOL CPU usage.<\/li>\n\n\n\n
- The Impact:<\/strong> By reclaiming these MSUs, the organization was able to support new workloads with their existing processing resources.<\/li>\n<\/ul>\n\n\n\n
Security and Integration<\/h3>\n\n\n\n
One of the most common questions regarding JOPAZ is how it interacts with existing mainframe security. JOPAZ is built to be a good citizen of the mainframe ecosystem:<\/p>\n\n\n\n
- \n
- Data Access: Uses already in place Db2, VSAM and Adabas Security mechanisms implemented.<\/li>\n\n\n\n
- Security: It leverages the Java security model while remaining fully compliant with standard mainframe security managers like RACF, TopSecret, and ACF2.<\/li>\n\n\n\n
- Operational Flow: Because it uses standard JCL (Job Control Language) to trigger the JVM execution, it fits seamlessly into existing scheduling and operations workflows.<\/li>\n<\/ul>\n\n\n\n
Phased Implementation<\/h4>\n\n\n\n
Start with a single, resource-heavy application, prove the impact of capacity savings, and then expand to other areas of the business. This phased approach eliminates the unpredictability of traditional modernization.<\/p>\n\n\n\n
Unlock the Power You Already Own<\/h4>\n\n\n\n
The mainframe remains the gold standard for stability, security, and enterprise transaction volume. With JOPAZ, you don’t have to leave the platform to modernize. You can reclaim your capacity, hit your SLAs, and dramatically reduce your CPU usage\u2014all while keeping your COBOL code exactly where it belongs.<\/p>\n\n\n\n
- The Impact:<\/strong> By reclaiming these MSUs, the organization was able to support new workloads with their existing processing resources.<\/li>\n<\/ul>\n\n\n\n
- With Two zIIP Engines:<\/strong> After seeing the initial success, they added a second zIIP engine. The CPU savings jumped to 92.9%.<\/li>\n\n\n\n
- With a Single zIIP Engine:<\/strong> They achieved a 76% reduction in batch C<\/strong>OBOL CPU usage on the GP.<\/li>\n\n\n\n
![\"Energy](\"https:\/\/www.softwareag.com\/app\/uploads\/2025\/06\/featured-image_energy-transfer_logo.png\"){kind=logo}
\n <\/div>\n ![\"Universit\u00e0](\"https:\/\/www.softwareag.com\/app\/uploads\/2024\/11\/featured-image_universita-cattolica-del-sacro-cuore_logo.png\"){kind=logo}
\n <\/div>\n