IMS COBOL and MFS Maps

AtomIQ analyzes IMS-DC COBOL and MFS map source so you can see how a transaction talks to the terminal and to IMS segments. Map preview renders MFS definitions (FMT / MSG)—not a live IMS Connect or 3270 session.

1. Import .mfs members with COBOL (Source Upload or upload-source-files).
2. Open a MAP resource to preview the device-format field grid.
3. Use message chips to scope the view to a MID (input), MOD (output), or the whole screen. When MFS declares NXT=, the chip shows the next expected descriptor.
4. Assign a screen type from the viewer. Workspace settings include a Mainframe (MFS) rule family, separate from CICS BMS.
5. IMS programs link to maps when the I/O area name matches an MFS MSG. CBLTDLI / AIBTDLI calls are classified as screen I/O or DL/I segment access (GET, ISRT, REPL, DLET).
6. From a saved UI Flow operation, walk PF-key branches, CHNG program/MOD switches, and SPA conversational carry from source. Hub upload remains the CICS + BMS path.

See [[feature:atomiq-ims-mfs-support|IMS COBOL and MFS maps]].