Import sources

The Import page offers three routes. Whatever you import becomes an operation in the active application: give it a name, and it appears in the sidebar as the active operation.

Import from AtomIQ

Browse operations from a connected AtomIQ instance, or upload an .atq export file. The AtomIQ URL is set in Global Settings; AtomIQ takes the shared mainframe login unless you give it its own account. The same import is available to agents over MCP: catalog { show: "atomiq" } lists the workspaces and their operations, and operation { source: { atomiq } } imports one. See Flow API and MCP.

Importing a batch job. A JCL job imports by the program its first EXEC PGM= step runs and for which the export carries source; a JCL-rooted operation names its program in a step, never in the job itself. A job whose steps only run utilities or cataloged procedures has nothing to convert, and says which steps it runs rather than that JCL is unsupported; the programs such a job compiles or defines import as their own operations.

Importing several operations at once. A batch import is best-effort: each operation is imported independently and reports its own outcome, so one failure does not discard the operations already brought in. Mixing a job with nothing to convert into a batch still imports the rest.

Import legacy source

Upload your own files: program source, screen maps, copybooks and an optional SQL schema. Several .cbl files make one operation of linked programs; the first one uploaded is the entry program. JCL is not a program type you upload directly here.

Program type	Required	Optional
CICS COBOL screen	.cbl source, .bms map	Copybooks (.cpy), schema.sql
IMS COBOL screen	.cbl source, .mfs format(s)	Copybooks, .psb, .dbd, schema.sql, .dlicols (only for CoreIQ runs)
RPGLE screen	.rpgle source, .dspf display file	Copy members, physical/logical files, schema.sql
COBOL RPC	.cbl source	Copybooks, schema.sql
RPGLE RPC	.rpgle source with exported procedures	Copy members, schema.sql

The console picks the language kit from the screen file: .mfs uses the IMS kit (MFS screens, SPA/message I/O, optional DL/I via PSB/DBD), .bms the CICS kit.

Import example

Built-in samples covering CICS COBOL/BMS, IMS COBOL/MFS, RPG screens, RPC modules, SQL, VSAM and IMS DL/I. A sample loads into the active application, so Load stays disabled until you create or select one in the header.

Sample	Type	What it demonstrates
cousr01	CICS COBOL screen + SQL	Single map screen browsing the USERSEC table by user ID: start here
usermenu	CICS COBOL screen + SQL	Three linked CardDemo screens (admin menu, user list, user detail), navigated with PF keys
add-transaction	CICS COBOL screen	Three-screen CardDemo add-a-transaction flow with F1 lookup maps, loaded from an AtomIQ .atq export
cics-acctfile	CICS COBOL screen + VSAM	Account inquiry over a KSDS: keyed READ, STARTBR/READNEXT browse, REWRITE
rpc-usersec	COBOL RPC	Headless USERSEC service: add a user, or look up and delete, over a commarea
rpc-acctview	COBOL RPC	CardDemo account chain: update an account and view balances
rpgle-dspf	RPGLE screen	Three CardDemo customer programs over a display file
rpgle-rpc	RPGLE RPC	RPG ILE service program exposing customer operations, no display file
ims-claim	IMS COBOL + MFS	Three MFS screens, DB2 policy lookup and claim insert: the IMS starter
ims-claim-real	IMS COBOL + MFS	Five MFS screens with a paginated claims list driven by keyset cursors
ims-policy	IMS COBOL + MFS	Seven-screen policy issuance with bank lookup and a rider catalog CALL: multi-program play with SPA handoff
ims-custroot	IMS COBOL + MFS + DL/I	Customer maintenance with GU/GHU/ISRT/REPL/DLET over a sample image
ims-carddemo	IMS COBOL + MFS + DL/I	CardDemo CUSTDATA → ACCTDATA hierarchy with packed-decimal balances
ims-carddemo-3lvl	IMS COBOL + MFS + DL/I	Three-level CardDemo including CARDDATA: card-list GNP walk, level-3 REPL and ISRT
ims-account	IMS COBOL (derived screen)	Non-conversational account inquiry; the screen is derived from the COBOL message records
ims-account-mfs	IMS COBOL + MFS	The same inquiry driven by a hand-written MFS format, with no SPA

What is supported

Platform	Source you supply	Coverage
CICS COBOL screens	.cbl + BMS .bms	Supported, including COMMAREA and EXEC SQL
IMS/DC COBOL screens	.cbl + MFS .mfs	Supported, conversational (SPA) and non-conversational
IMS/DC without an MFS	.cbl only	Supported: the screen is derived from the message records
IMS DL/I databases	.psb + .dbd	GU/GHU/GN/GNP/ISRT/REPL/DLET, SSAs qualified on any segment field, up to 3-level hierarchies; add a .dlicols map for a live database through CoreIQ
RPGLE screens	.rpgle + DSPF .dspf	Supported, including subfiles
RPC / batch modules	COBOL or RPGLE NOMAIN	Invoked with input/output commareas
DB2 SQL	EXEC SQL in any of the above	Supported, including cursors and paginated list screens