OL AtomIQ
Your z/OS or IBM i monolith decomposed one piece at a time
OL AtomIQ imports COBOL, RPG, copybooks, JCL, and screen maps, builds a graph of programs, data, and dependencies, and finds the business operations and domains inside it. Teams decouple domains into separate apps and route the remaining cross-app calls through a gateway, so each step is explicit, approvable, and reversible.
How it works
Bring the estate in, understand it, then decompose it
01Bring it in
Import from z/OS and IBM i
Import source from IBM RSE, JZOS, CICS CMCI, OL CoreIQ, JT400 on IBM i, file upload, or zipped packages. Large and messy source trees are staged, duplicates are handled, and long-running jobs are tracked in their workspace.
02Understand it
See programs, data, and dependencies
Group programs into apps on an interactive canvas, read source with AI-generated documentation, preview BMS, MFS, and DSPF maps from source, and trace a DB2 column, IMS segment, or file field across programs and copybooks.
03Decompose it
Decouple along business processes
Identify operation roots and call trees, suggest domains from operation groups, apply decomposition rules, and register, approve, publish, and unpublish the cross-app routes that remain.
Key features
A graph-driven path from monolith to domains
01 / IMPORT
Multi-source import
RSE, JZOS, CICS CMCI, Hub Planner, OL CoreIQ, JT400, file upload, or zipped packages, all analyzed through the same workspace pipeline.
02 / IBM I
AS/400 (IBM i) and RPG
JT400 source import, DB2 for i metadata, RPG and CL analysis in the same graph as COBOL, and DSPF map preview from display-file source.
03 / CANVAS
Interactive App Viewer
Organize programs into apps by business usage on a drag-and-drop canvas, focus dependency arrows, filter, zoom, and save the layout.
04 / SOURCE
Source analysis and viewers
COBOL with AI-generated documentation, DB2 table metadata, file layouts resolved in the context of the job step, and JCL procedure input.
05 / LINEAGE
Data lineage
Follow a DB2 column, IMS segment, or file field through COBOL host variables across programs and copybooks, with read and write paths kept apart.
06 / IMS · RC
IMS COBOL and MFS maps
Preview MFS device formats, classify DL/I calls as screen I/O or segment access, and walk conversational transaction flow from source.
07 / OPERATIONS
Operations and domains
Find operation roots with heuristics or AI, review each call tree, and turn saved operation groups into candidate domains.
08 / ROUTING
Modernization rules and routing
Rule-based decomposition suggestions, and a register, approve, publish, and unpublish lifecycle for every cross-app route in the AtomIQ Gateway.
Video / Operation discovery
Discover insurance operations and refine the spec
AtomIQ Operation Discovery lists insurance transactions seeded from a CSD, then opens the COBOL and BMS source behind an Add Appeal step. OL Spec turns that analysis into shared models for Appeal, Client, Policy, and Complaint, and an agent is asked to mark Appeal level as required before both changed files are reverted.
Screens to APIs · RC
Screen flows from source, not from recordings
Map UI analysis reads COBOL and BMS or MFS map usage and builds the UI state machine from the points where a program sends, receives, or changes screens. For CICS with BMS, the analyzed flow uploads to OL Integration as a terminal Screens Flow in one step, without a live terminal session.
AI and MCP · RC
A graph-aware assistant and a built-in MCP server
The Graph Assistant answers questions about apps, resources, and operations from the live workspace graph. The MCP server exposes the same actions as the UI, so AI coding assistants can query the graph, identify operations, suggest domains, analyze UI flow, and upload Screens Flows. On z/OS and IBM i, MCP sessions authenticate against RACF or IBM i credentials.
Video / Source analysis
From AtomIQ screens to OL Spec and App Player flows
Starting in AtomIQ, the walkthrough inspects DB2 table metadata and opens a UI Flow view that links CICS screens to embedded SQL reads on account-related tables. It continues in OL Spec with an imported Accounts business process, flowchart, and data concepts, and finishes in App Player by running search criteria against generated pages.
Part of the platform
Works with OL CoreIQ and OL Integration
OL CoreIQ supplies catalogs and record layouts, and AtomIQ pushes the dataset layouts it finds in source back to CoreIQ, so those datasets can be browsed, tested, and exposed as APIs without hand mapping. OL Integration runs the Screens Flows AtomIQ generates. AtomIQ can also run beside an on-prem OL Hub with Hub sign-in.
Get started fast
Demo workspaces and an in-product API reference
Ready-made CICS insurance, retail banking, and IBM i card management workspaces are analyzed at startup through the same pipeline as customer source, so teams can explore before connecting a host. The API Reference documents the REST endpoints and MCP tools inside the product.
At a glance
Every step explicit, approvable, and reversible
Import sources
RSE, JZOS, CICS CMCI, Hub Planner, OL CoreIQ, JT400, file upload, and zipped packages.
Platforms in one graph
z/OS and IBM i, with COBOL, RPG, and CL analyzed side by side.
Map types previewed from source
BMS, MFS, and DSPF, without a live terminal session.
Route lifecycle steps
Register, approve, publish, and unpublish every cross-app call.
ECOSYSTEM
Built for the estates you already run
Mainframe and IBM i source on one side, the OpenLegacy platform on the other.
FAQ
Common questions
Which platforms and languages does AtomIQ analyze?
z/OS and IBM i. AtomIQ analyzes COBOL, RPG, RPGLE, and CL, along with copybooks, JCL and procedures, DB2 metadata, and BMS, MFS, and DSPF screen maps.
Does AtomIQ need a live terminal session?
No. AtomIQ previews maps and derives screen flows from their source definitions. It does not run live 3270 or 5250 sessions.
How does decoupling stay safe?
Domains are built from named business operations, and every call that crosses a new app boundary becomes a gateway route that is registered, approved, published, and can be unpublished to roll it back.
Can AI assistants work with AtomIQ?
Yes. A built-in MCP server exposes the same actions as the UI, and on z/OS and IBM i, MCP sessions authenticate against RACF or IBM i credentials.
Can we try it before connecting our host?
Yes. Demo workspaces for CICS insurance, retail banking, and IBM i card management are analyzed automatically at startup.
Map your monolith before you move it
Tell us about your z/OS or IBM i applications, and we will set up a working AtomIQ session on your source.
Thanks — we received your message.
Something went wrong. Please try again.