Getting started

OL Screener exposes screen-based legacy applications as APIs so consumers never deal with 3270/5250 terminals. The web console focuses on remote CICS over MQ (OLGATE) and IMS Connect (preview).

Typical workflow

1. Create an application — pick Remote screen backend: CICS (MQ) or IMS Connect. This choice is required and cannot be changed later.
2. Create an operation — maps, Player sessions, and Screen APIs belong to the selected operation.
3. Configure connection — set CICS/MQ or IMS Connect under Global Settings. Configure Mainframe (import maps) or AtomIQ (import maps) when you need those sources.
4. Import — files, mainframe RSE or JZOS, AtomIQ, or a built-in sample. Descriptors are stored per operation.
5. Play — open Player, check readiness, and interact with live screens. Re-open the session after you import maps.
6. Screen APIs — record or author ScreenFlow scripts and expose them as named-field APIs.

Quick start (CICS over MQ)

1. Header dropdown → New application…. Set Remote screen backend to CICS (MQ).
2. Create an operation in the sidebar (or keep the one created with a sample).
3. Global Settings (gear) → CICS / MQ (remote screen) → Save.
4. Import → Import example, pick aq00, click Load.
5. Start the AQ00 transaction on the mainframe.
6. Player → confirm readiness → Play, or run the seeded flow from Screen APIs.

For IMS Connect, create the application with backend IMS Connect, configure IMS Connect (remote screen), and load clmm01. Set Play start (Entry MID / Trancode) if the sample does not already fill it.

Navigation

Sidebar pages (most need an active operation): Import, My Maps, Player, Screen APIs. The header has the application selector, Help, and Settings. Operations for the current application appear under the sidebar links.