Mas essas abordagens s\u00e3o repletas de riscos. Elas frequentemente envolvem custos imprevis\u00edveis, longos prazos de implementa\u00e7\u00e3o e perda de funcionalidades quando o novo sistema n\u00e3o consegue replicar d\u00e9cadas de l\u00f3gica de neg\u00f3cio incorporadas no c\u00f3digo COBOL original. Al\u00e9m disso, muitas vezes s\u00e3o solu\u00e7\u00f5es \u201ctudo ou nada\u201d, o que significa que, quando a moderniza\u00e7\u00e3o encontra um obst\u00e1culo, geralmente j\u00e1 \u00e9 tarde demais para reconsiderar.<\/p>\n\n\n\n
Uma nova abordagem: recuperando a capacidade do GP com JOPAZ<\/h3>\n\n\n\n
O JOPAZ oferece uma alternativa n\u00e3o disruptiva. Em vez de sair do mainframe, o JOPAZ mant\u00e9m voc\u00ea na plataforma enquanto reduz significativamente a carga sobre os processadores gerais. Ele faz isso tornando as cargas de trabalho em lote COBOL eleg\u00edveis para execu\u00e7\u00e3o nos processadores IBM zIIP.<\/p>\n\n\n\n
Com as cargas de trabalho sendo executadas no zIIP, as organiza\u00e7\u00f5es podem liberar imediatamente capacidade de GP para outras tarefas de alta prioridade.<\/p>\n\n\n\n
Como o JOPAZ funciona: Internamente<\/h3>\n\n\n\n
A transi\u00e7\u00e3o de uma carga de trabalho COBOL em lote padr\u00e3o para uma carga de trabalho eleg\u00edvel ao zIIP acontece em quatro fases:<\/p>\n\n\n\n
- \n
- Identifica\u00e7\u00e3o: Identificar batch de trabalho que est\u00e3o consumindo mais recursos de GP.<\/li>\n\n\n\n
- Compila\u00e7\u00e3o: o JOPAZ utiliza seu c\u00f3digo-fonte COBOL existente e o compila diretamente em bytecode Java.<\/li>\n\n\n\n
- Execu\u00e7\u00e3o: esse bytecode \u00e9 executado em uma Java Virtual Machine (JVM), tornando a carga de trabalho apta a ser processada pelo engine zIIP.<\/li>\n\n\n\n
- Escala: repetir com quantos batch de trabalho forem necess\u00e1rios. O JOPAZ \u00e9 uma abordagem em fases para otimiza\u00e7\u00e3o de cargas de trabalho, mantendo o seu neg\u00f3cio funcionando normalmente.<\/li>\n<\/ol>\n\n\n\n
De forma cr\u00edtica, nenhuma altera\u00e7\u00e3o no c\u00f3digo COBOL \u00e9 necess\u00e1ria. Sua l\u00f3gica de neg\u00f3cio permanece intacta, e seus desenvolvedores continuam trabalhando no ambiente que j\u00e1 conhecem.<\/p>\n\n\n\n
Resultados no mundo real<\/h3>\n\n\n\n
Estudo de caso 1: fornecedor de energia do varejo<\/strong><\/h4>\n\n\n\n
Essa organiza\u00e7\u00e3o enfrentava dificuldades com cargas de trabalho intensas em DB2. Eles implementaram o JOPAZ para avaliar qu\u00e3o eficaz ele poderia ser no processamento de jobs em lote com alta depend\u00eancia de banco de dados.<\/p>\n\n\n\n
- \n
- Com um \u00fanico zIIP Engine:<\/strong> Foi alcan\u00e7adouma redu\u00e7\u00e3o de 76%<\/strong>no uso da CPU de COBOL no 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
- Com um \u00fanico zIIP Engine:<\/strong> Foi alcan\u00e7adouma redu\u00e7\u00e3o de 76%<\/strong>no uso da CPU de COBOL no 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