Products / OL Next
OL Next
Move COBOL and RPGLE screen and RPC programs (CICS/BMS, IMS/MFS, IBM i/DSPF) off the host as runnable code on the JVM, validate them in the browser, and expose them as REST APIs while data stays on the host.
OL Next moves legacy screen and RPC programs off the host without rewriting them. It converts COBOL and RPGLE programs, together with their CICS BMS, IMS MFS, or IBM i DSPF maps, into runnable legacy code on the JVM. Teams keep editing the original COBOL or RPGLE in OL Next, run and validate the converted programs in the browser, and expose them as REST APIs. Business logic can leave the host first, while the data stays where it is until a data migration is ready.

Key capabilities
-

CICS
CICS COBOL / BMS migrationConvert CICS COBOL screen programs with BMS maps into runnable legacy code on the JVM you can play in OL Next, map player, not a 3270 terminal.
-

API
DB access managementPoint replatformed programs at an H2 sandbox (schema.sql / seed.sql), a live host store (DB2, VSAM, IMS-DB via JDBC or CoreIQ APIs), or a modern DB after data migration, so logic can leave the host before data does.
-

COBOL
IMS COBOL / MFS migrationConvert IMS DC COBOL programs with MFS maps into runnable legacy code on the JVM you can play and validate in OL Next. MFS map conversations, not 3270.
-

AS/400
Interactive program playerRun converted map-based screen programs in the browser (map-layout grid, AID keys, and run log) with no mainframe and no 3270/5250 terminal session.
-

API
Map screen flowsAuthor map ScreenFlows with explicit I/O, expose via OpenAPI, and record/run/debug against converted map programs, not Hub terminal Screens Flows.
-

AI
MCP server for AI agentsLet an AI agent take a legacy program from source to a working API over the Model Context Protocol: convert, run screens and RPC programs, record or generate flows, and bind live host data.
What it enables
OL Next moves legacy screen and RPC programs off the host without rewriting them. It converts COBOL and RPGLE programs, together with their CICS BMS, IMS MFS, or IBM i DSPF maps, into runnable legacy code on the JVM. Teams keep editing the original COBOL or RPGLE in OL Next, run and validate the converted programs in the browser, and expose them as REST APIs. Business logic can leave the host first, while the data stays where it is until a data migration is ready.
Part of the OpenLegacy platform
Run it from one governed plane
Govern, deploy, and operate this product with the rest of the suite — managed or on-prem.