OL TermIQ
3270 and 5250 screens to operations, insight, and APIs
See how your terminal applications are really used. OL TermIQ records sessions, catalogs screens, identifies and measures business operations, and turns real journeys into terminal screens flows that OL Integration publishes as APIs.
How it works
Everything is based on recorded user traffic
01Record and catalog
Turn sessions into a screen catalog
Capture live sessions from OL Terminal through a workspace webhook, or upload trail files. TermIQ stores screens, snapshots, and terminal events, and you name, tag, and publish the screens, by hand or with AI.
02Identify and measure
Find the business operations
Define operations such as open account or inquire balance with start, end, and reset triggers. TermIQ tracks every run as traffic arrives, backfills matches from past recordings, and reports on duration, steps, and state.
03Turn journeys into APIs
Generate terminal screens flows
Select up to ten completed runs of an operation, let AI derive the happy path, and create the project, module, method, contract, and trail that OL Integration uses for a terminal screens flow.
Key features
From recorded terminal traffic to a governed catalog
01 / RECORD
Terminal event recording
Live webhook snapshots or uploaded trails become screens, snapshots, and terminal events you can filter, group by session or user, and export as CSV.
02 / REPLAY
Session and trail viewing
Step through a recorded session or a trail file, see which fields the user changed, leave notes, and mark where an operation starts and ends.
03 / CATALOG
Screen discovery and model mapping
Name, tag, and publish screens, map their fields to OL Hub global models, and fill field names from a matching BMS, MFS, DDS, or DSP map.
04 / AI
AI screen identification and merge
An LLM names and describes each screen from several snapshots after per-session values are masked, then duplicate screens are merged into one.
05 / OPERATIONS
Operation definitions
Write start, end, and reset triggers by hand, draft them from a session range, or accept operations TermIQ suggests from repeated patterns.
06 / INSTANCES
Operation instance collection
Every run tracked live during ingest or backfilled from history, with duration, steps, and the events in between, exportable as a trail.
07 / REPORTS
Runtime reporting and dashboard
Built-in and custom reports over events, operations, and sessions, with charts, rolling date windows, drill-down, Excel export, and pinned dashboards.
08 / MCP
MCP agent tools
MCP tools search and change the catalog, and terminal tools sign in to a live TN3270 or TN5250 session or play a stored trail instead of a host.
Video / TermIQ basics
Connect, catalog, and run MCP tool calls
A workspace and connection are created, the webhook URL goes into the terminal configuration, and normal work on the host is recorded. New screens are parsed into a catalog, reviewed, and published for AI analysis. A sign-on macro lets an AI client sign in and run terminal MCP tool calls against the live host, and the result is an operation definition with its task, input fields, and start and end screens.
AI with masking
Session values stay on the tenant
Before a screen is sent to the model, TermIQ compares its snapshots and masks the cells that change between sessions: letters become X and digits become 9. Labels, banners, and titles stay readable, so the model can still name the screen. The original snapshot is never overwritten.
MCP for agents
A catalog server and a terminal server
Catalog tools read events and sessions and manage workspaces, screens, maps, operations, reports, and settings. Terminal tools list connections, sign on, read the screen, set fields, press a key, and record a trail. Host credentials are kept encrypted for the sign-in lifetime, and trail playback never contacts a host.
Video / Operation definitions
Mark a session and create an operation
In TermIQ Runtime, recorded events already name screens such as sign-on, the IBM i main menu, user tasks, and job attributes. The Session Viewer marks where the operation starts, Create Operation Definition takes the selected events and asks for a process name, and the new operation appears on the Operations tab.
AI flow analysis
Real runs become terminal screens flows
Select one to ten completed instances and run flow analysis over their terminal events, including recorded notes. A repeated screen cycle can become a loop, a list row selection can become an expression step, and an error path can be published as a separate output. Created flows are kept so you can open them again.
What OL TermIQ is not
Traffic, not source code
TermIQ analyzes recorded terminal traffic. An uploaded screen map can name the fields on those screens, but TermIQ does not derive flows by reading program source. To derive screen flows from COBOL and BMS or MFS maps, use OL AtomIQ. To run converted map programs off the host, use OL Next.
Video / Journey to API
Turn a recorded session into a Hub flow
The walkthrough imports a recording, builds the screen catalog with AI analysis, defines the operation by marking its start and end, and finds its past runs. The last step names the Hub method, selects the host type, and creates the project and screens module.
At a glance
Grounded in how the application is used
MCP tools
Twenty-five for the catalog and recorded data, seven for live or mock terminal sessions.
Completed runs per flow analysis
AI derives the happy path from real operation instances.
Built-in reports
Operation state, duration, and steps, session duration and state, and transaction errors.
Deployment shapes
SaaS with Hub IAM, on premises with Keycloak, or a lite install on a trusted network.
ECOSYSTEM
Works with the terminal applications you already run
IBM Z and IBM i screens, connected to the rest of the OpenLegacy platform.
FAQ
Common questions
How does TermIQ get terminal traffic?
From live sessions in OL Terminal through a workspace webhook, or from uploaded OpenLegacy trail files. Both IBM Z (3270) and IBM i (5250) sessions are supported.
What does the AI see?
For screen identification, cells that change between snapshots of the same screen are masked before the model is called. Labels, banners, and titles stay readable, and the original snapshot is kept unchanged.
Does TermIQ read program source?
No. TermIQ works from recorded traffic. An uploaded BMS, MFS, DDS, or DSP map can name the fields on recorded screens. To derive flows from source, use OL AtomIQ.
Can AI agents use TermIQ?
Yes. TermIQ exposes MCP tools that search and change the catalog, and terminal tools that sign in to a live TN3270 or TN5250 session or play a stored trail as a mock session.
Where does TermIQ run?
As SaaS with Hub IAM, on premises with Keycloak, or as a lite install for a trusted network. A process can also run API-only, or with design changes locked while design is imported from QA.
See how your terminal applications are really used
Tell us which 3270 or 5250 applications your teams work in, and we will set up a working demo.
Thanks — we received your message.
Something went wrong. Please try again.