Glossary
Glossary
| Term | Definition |
|---|---|
| App | A set of resources in the same technology stack (LOGIC=COBOL, DB=SQL, Files=file storage, Jobs=batch). Shown as a box in the App Viewer. |
| App pair | Two apps that have connections between them (for example "Customer → Account"). |
| AtomIQ Gateway | A centralized routing point through which cross-app dependencies are managed and API calls are proxied during modernization. |
| BMS | Basic Mapping Support: the CICS screen definition format used to describe 3270 terminal screens. |
| Bounded Context | A Domain-Driven Design concept describing the boundary within which a particular domain model is defined and applicable. |
| CBLTDLI / AIBTDLI | IMS-DC COBOL call interfaces. AtomIQ classifies these as screen I/O or DL/I segment access. |
| CICS | Customer Information Control System: IBM transaction processing system for mainframe applications. |
| CMCI | CICS Management Client Interface: REST API for managing and querying CICS resources. |
| Connection | A dependency relationship between two resources (from → to), representing a program call, data access, or other interaction. |
| CoreIQ | OpenLegacy's mainframe asset discovery platform providing host, catalog, and record layout information. |
| Data Lineage | The traced path of data from a DB2 table column, IMS segment field, or file field through COBOL host variables and across programs and copybooks. |
| Decoupled app | A decoupled LOGIC app separated from the monolith with dependencies routed through the gateway. |
| DL/I | IMS data language. Segment GET, ISRT, REPL, and DLET operations appear on the graph and in lineage. |
| 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. |
| DSPF | Display File: the IBM i DDS screen definition format used to describe 5250 terminal screens. |
| Enrichment | Structured metadata attached to a resource (one-liner summary, business objects, program interface), generated from source analysis or AI. |
| File Layout | A FILE → copybook relationship discovered during import (FILE_LAYOUT), linking a dataset or file to its record structure. |
| Graph Assistant | An AI-powered chat panel in the App Viewer that answers questions about the application dependency graph using workspace context. |
| Hub Planner | OpenLegacy's planning tool for managing modernization baselines and environments. |
| IMS | IBM Information Management System. AtomIQ analyzes IMS-DC COBOL and MFS maps from imported source. |
| JT400 | IBM Toolbox for Java: the API used for IBM i source import, DB400 JDBC, and optional host sign-on. |
| JZOS | IBM's Java z/OS runtime extension for direct access to z/OS datasets and services. |
| MCP | Model Context Protocol: AtomIQ's built-in tool server so AI assistants can drive the same actions as the UI. |
| MFS | Message Format Service: the IMS screen definition format (device format FMT plus MID/MOD message descriptors). |
| MID / MOD | MFS input (MID) and output (MOD) message descriptors bound to a device format. |
| Modernized app | A cloud-native version of a decoupled app with REST API endpoints replacing legacy program calls. |
| OL Parser JSON | OpenLegacy Entity/Operation descriptor JSON used to parse COBOL linkage field definitions for enrichment and documentation. |
| Operation | A saved call hierarchy rooted at a resource (UI Flow, Service, or Batch) used for impact analysis, domain suggestions, and screen-flow automation. |
| Published Route | A routed connection made available through the AtomIQ Gateway for active traffic routing. |
| Resource | A program, copybook, JCL procedure, BMS or MFS map, DB2 table, IMS segment, or other asset within an app. |
| Routed Connection | A dependency that has been registered to route through the AtomIQ Gateway. |
| RPG | IBM i business language. AtomIQ recognizes RPG/RPGLE members and routes them through the RPG analysis pipeline. |
| RSE | Remote System Explorer: IBM's REST API for accessing z/OS resources (datasets, UNIX files, JES jobs). |
| Screen Flow | Code-first UI state machine derived from COBOL plus BMS or MFS source. For CICS + BMS, uploadable to Hub as a terminal Screens Flow. |
| Workspace | An isolated environment in AtomIQ containing its own workspace data, connections, settings, and configuration. |
Definitions of the terms used in OL AtomIQ.