What's new

MongoDB connections, with an explorer and a console

MongoDB is now a connection type of its own, stored beside the SQL databases OL DataIQ already manages and listed with them. The connection takes a mongodb:// or mongodb+srv:// connection string, with an optional username, password and auth database, TLS, and a default database that preselects itself when the console a

Import managed users with multiple printer queues

A managed IBM i user can now have several output queues, independent of how many concurrent sessions they are allowed. CSV import accepts a comma-separated printerQueue list; the user editor lets you add or remove queues. Single-queue rows still import, and an empty list falls back to the connection then global printer

Record trails as JSON or IDE XML

Administrators can choose the session recording format in Settings. JSON remains the default for playback, trail notes, and OL Integration upload. IDE-compatible XML writes and plays the legacy terminal-trail document used by older OpenLegacy IDE versions. XML recordings cannot be uploaded as Integration trail assets,

Command-level CICS assembler map programs in Player and ScreenFlow

OL Screener can prepare command-level CICS assembler map programs for remote play, import their BMS maps, and run the conversation in Player and ScreenFlow over IBM MQ—the same named-field path used for COBOL map programs. Teams classify eligibility, write OLSCREENER twins to a PDS, and compile on RSE when JCL is confi

Standalone, on-prem, and lite deployment bundles

TermIQ now derives its deployment shape from standard environment configuration—SaaS with Hub IAM, on-prem with Keycloak, or lite standalone for trusted-network installs. Installable on-prem and lite bundles ship with the service, frontend, and database migration job for repeatable deployments.

Richer report fields from screen tags and positions

Reports can now use field-level dimensions derived from screen tags and snapshot field positions, so analysts can group and filter on labeled inputs without maintaining separate field lists. Builtin and custom reports share the same execution, drill-down, and Excel export paths.

Suggested operation definitions from session scans

TermIQ periodically scans recorded sessions and suggests operation definitions with proposed names and start-to-end screen pairs. Review suggestions on the Operation Definitions page, create a definition in one click, or dismiss suggestions you do not need. Scan interval is configurable in Application Configuration; yo

MCP tools for terminal discovery and live sessions

TermIQ now exposes thirteen MCP tools for AI agents and automation. Seven read-only tools search recorded terminal events, describe catalog screens, list sessions, run reports, and show screen transitions. Six additional tools open live TN3270 or TN5250 sessions using workspace terminal connection profiles—read the cur

Faster legacy imports, and large IMS segments that finish

Two changes to how an import reads its source, each measured rather than assumed. VSAM datasets can be paged by record key instead of by counting from the start of the dataset. Paging by count makes every page pay again for the records ahead of it, so a scan gets slower the further it goes; paging by key does not. On a

See what a batch import actually cost, and export it

A batch execution now reports how it read: records and pages, throughput, how much of the working time went on waiting for the source, megabytes transferred, and — per step — the split between remote wait and local work, page latency at p50, p95 and max, and the cost of a page plotted against how far the scan has got.

Play CICS file-control programs against real VSAM datasets

VSAM is now a host engine of its own. A program that reads records rather than rows binds its CICS FILE operands to datasets in the application's settings — one row per FILE the program declares, so the map cannot drift from the copybook — and a blank dataset is refused by name rather than silently falling back. DATASE

Installable on-premises and Lite bundles

OL Next ships as a bundle you can install yourself, in two shapes. Unzip it, copy the example environment file — every value you must set is marked — and bring it up with the compose file for the shape you want. Each bundle carries its own README, build notes, and a list of every environment variable that shape reads.

Host connections are shared, and CoreIQ endpoints are picked from a list

Connections to a host now live on their own page and are created once, then reused by every application. Each has a reach — direct JDBC, or through OL CoreIQ — and an engine that is discovered rather than typed: a JDBC connection reports its own engine when you test it, and a CoreIQ connection takes its engine from the

Updated in-product help for applications, import, and remote play

The built-in help guide now matches the current console. New sections cover creating applications and operations, the four map import paths, Prepare COBOL, Player and Screen APIs, and Global Settings including database options.

Reach host DB2 through CoreIQ, on z/OS and on IBM i

A converted program's embedded SQL can now run against real host DB2 through OL CoreIQ, without a JDBC driver or a direct route to the database. Both DB2 for z/OS and DB2 for i are reachable: the engine follows the endpoint the connection points at, so an IBM i host is configured exactly like a mainframe one.

Import a batch job by the program its step runs

A JCL job used to be turned away on its type alone, so a batch job could never be imported however much source it carried. It is now judged on content: the job's steps are read, and the first step naming a program the export has source for becomes the operation's entry program — which is how a JCL-rooted operation work

Run IMS DL/I programs against a live IMS database

A DL/I call names a field as the DBD spells it, while CoreIQ's IMS endpoint runs IMS Universal JDBC and exposes the IMS catalog's own column names. The two describe the same segment and neither side can guess the other's spelling, so an operation that runs against live IMS now ships a per-segment map from DBD field nam

Recorded trails stay in-bounds for screen-flow import

Session recordings now keep the AS/400 connection they were captured on, so admin session and trail lists match per-connection user management. JSON trails used as OL Integration trail assets are normalized before export: screen size and cursor stay inside the visible grid, and fields that ran past the last cell are sp

Assigned output queues for managed users

When a managed user is granted specific IBM i output queues, the printer panel can search only those queues. Device-location filters are blocked in that mode, and preview, PDF download, and delete are allowed only for spooled files that actually sit on an assigned queue. Users without assigned queues keep the previous

Per-connection user management for IBM i

Administrators now provision managed users, identity policy, device names, and session limits for each AS/400 connection instead of one global list. JWT, Kerberos, and trusted-header settings follow the selected connection, so one host can require external identity while another stays open. Import and export users with

Keyed-cursor paging for VSAM datasets

View File and the published VSAM dataset API now page keyed datasets by cursor instead of a numeric offset. Each next page starts after the last key on the current page, so a record inserted or deleted elsewhere in the file does not skip or repeat rows. Invalid keys are rejected instead of silently restarting from the

MCP on mainframe and IBM i deploys

The AtomIQ MCP server now advertises the real host base URL on z/OS and IBM i installs, so assistants can reach the in-host endpoint instead of a loopback address. Host sign-on validates with native RACF when RSE is not configured, and IBM i checks fail closed if JT400 is unavailable. MCP session identity is separate f

IMS-DB table REST APIs

Select IMS-DB segments in Populate APIs, choose read and write operations, and publish them from the IMS-DB catalog as REST Data APIs. Bodies can be the columns the database declares or a COBOL copybook layout. Child segments keep their parent keys, pages use a cursor instead of an SQL offset, and published operations

Remote IMS-DLI and saved JCL templates

Add an IMS-DLI-REMOTE endpoint to browse PSBs and view hierarchical segments through OL Z Gateway—the same workbench as local DL/I, without installing CoreIQ on z/OS. Persist custom JCL templates per endpoint and PSB, and edit them from Host Explorer when the endpoint allows user template edits.