Future-Proof Your Mainframe:
Unlocking Unused zIIP Capacity for Growth

ウェビナー

このウェビナーで学べること

• How JOPAZ compiles COBOL applications into Java bytecode for zIIP-eligible execution
• How an existing COBOL batch program accessing a database is compiled and executed with JOPAZ
• How COBOL application behavior is preserved during execution
• How to remotely debug a COBOL program running on z/OS using Eclipse on a PC

Moving COBOL batch processing from general-purpose processors to specialty engines sounds compelling, but for mainframe teams, the important question is: How does it actually work?

In this technical deep dive, we’ll demonstrate how existing COBOL batch applications can be compiled and executed as zIIP-eligible Java workloads on z/OS, without changing the COBOL source code or manually refactoring the application.

We’ll examine the complete execution path, from COBOL-to-Java bytecode translation through runtime execution on z/OS. We’ll also look at how JOPAZ handles database access and integrates with the operational environment surrounding existing COBOL batch applications.

Rather than replacing established production processes, JOPAZ is designed to work within them. Existing JCL, scheduling systems, and operational controls remain in place while eligible application processing is redistributed to zIIP.

If you work with COBOL, z/OS, databases, batch processing, or mainframe performance and capacity, this session will give you a technical view of what happens when an existing COBOL workload is moved from general-purpose processing to zIIP with JOPAZ.