Overview and Key Concepts

OL AtomIQ is an enterprise platform that accelerates legacy mainframe (z/OS) and IBM i (AS/400) modernization through domain-driven decomposition, visual dependency management, and automated API routing. It provides the analytical and operational tooling to safely deconstruct monolithic COBOL/CICS and IMS-DC workloads into discrete, independently deployable apps aligned to business areas, without disrupting mission-critical transaction processing.

How AtomIQ helps

• Automated discovery: scan and import mainframe and IBM i assets (COBOL programs, copybooks, JCL, BMS and MFS maps, CICS transactions, RPG) through RSE, JZOS, JT400, or file-based import.
• Visual app decomposition: an interactive canvas where architects organize programs into bounded business areas, visualize cross-app dependencies, and plan decomposition.
• Source analysis and documentation: COBOL source with inline enrichment, AI-generated documentation, deterministic program summaries, map preview (BMS / DSPF / MFS), and data lineage from DB2 columns, IMS segments, and file fields through host variables.
• Dependency routing: register and publish cross-app dependencies through the AtomIQ Gateway, enabling controlled decoupling of the monolith.
• AI-powered assistance: a graph-aware chat assistant, batch documentation, resource enrichment, and AI-driven operation identification.
• Modernization path: map legacy resources to modern API endpoints, bridging mainframe operations and cloud-native microservices.

Key capabilities

• Interactive App Viewer: drag-and-drop canvas for organizing programs into apps by business usage area, with color-coded dependency arrows, real-time filtering, workspace persistence, and theme support.
• Multi-source import: IBM RSE, JZOS, CICS CMCI, Hub Planner, CoreIQ record layouts, JT400 (IBM i RPG/COBOL/CL), or file upload (JSON, source).
• Source analysis and documentation: multi-tab source viewer with COBOL source, BMS/DSPF/MFS map preview, file layouts, AI-generated documentation, and deterministic program summaries (one-liners, business objects, program interface).
• Data lineage: track data flow from DB2 columns, IMS segments, and file fields through COBOL host variables and across programs and copybooks, in an interactive tree with source-context preview.
• Graph Assistant: AI chat embedded in the App Viewer for context-aware answers about the dependency graph, resources, and architecture.
• Dependency routing engine: register, approve, publish, and unpublish routes through the AtomIQ Gateway.
• Modernization rules engine: automated rules that analyze app structures and suggest decomposition strategies.
• Map preview (BMS, DSPF, MFS): preview CICS BMS, IBM i DSPF/DDS, and IMS MFS map layouts from source (not a live terminal), link maps to programs, and assign screen types.
• Operation Viewer: hierarchical call tree from a resource (UI Flow, Service, or Batch view). Save operations, reopen them from Manage Operations, and decouple from the tree.
• Screen Flow (code-first): analyze a UI state machine from COBOL plus BMS or MFS source. For CICS + BMS, upload a terminal Screens Flow to Hub. No live 3270 or IMS Connect session is needed in AtomIQ.
• AS/400 (IBM i) and RPG: JT400 import, DB400 metadata, DSPF display-file preview, RPG analysis pipeline, and platform-adaptive settings alongside z/OS.
• IMS COBOL and MFS: import .mfs maps, preview device formats and MID/MOD messages, classify CBLTDLI/AIBTDLI as screen I/O or DL/I, and walk conversational UI flow from source.
• Resource references: all incoming references to a resource and the saved operations that include it.
• AI documentation and enrichment: generate and regenerate documentation for single resources or in batch; enrichment fields appear across the UI.
• Multi-workspace support: isolated environments for different modernization projects, environments, or client engagements.

Key concepts

• Workspace: an isolated environment containing workspace data, connections, settings, and configuration.
• App: a set of resources in the same technology (LOGIC=COBOL, DB=SQL, Files=file storage, Jobs=batch), shown as a box in the App Viewer.
• Domain: a business, infrastructure, or common area that may contain several apps in different technologies. Apps with the same usage value belong to the same domain.
• Resource: a program, copybook, JCL procedure, BMS or MFS map, DB2 table, IMS segment, or other asset within an app.
• Connection: a dependency between two resources (from → to): a program call, data access, or other interaction.
• Routed connection: a dependency registered to route through the AtomIQ Gateway.
• Published route: a routed connection made available through the gateway for active traffic.
• Decoupled app: a LOGIC app separated from the monolith with its dependencies routed through the gateway.
• Modernized app: a cloud-native version of a decoupled app with REST API endpoints replacing legacy program calls.
• App pair: two apps with connections between them (for example "Customer → Account").
• Enrichment: AI or deterministically generated metadata on a resource: one-liner, business objects, and program interface.
• Data lineage: the path data takes from a DB2 column, IMS segment field, or file field through COBOL host variables, across programs and copybooks.
• Graph Assistant: an AI chat panel in the App Viewer that answers questions using the current workspace graph context.

Target use cases

• Mainframe-to-cloud migration planning: decompose monolithic COBOL/CICS/IMS-DC applications into independently deployable apps ahead of a cloud or microservices migration.
• Domain-driven design for legacy: define bounded contexts within an existing mainframe or IBM i portfolio.
• API gateway integration: establish controlled API routing between legacy and modern systems through the AtomIQ Gateway during the transition.
• Impact analysis: understand which programs, copybooks, maps, and batch jobs a proposed change affects, using the Operation Viewer and Data Lineage.
• Regulatory compliance and audit documentation: document decomposition, dependency chains, and enrichment metadata for auditors and regulators.