What's new

Batch runs: queue, stop, pause and continue, and rerun

A batch import from CoreIQ, from a VSAM dataset or an IMS segment, no longer has to run to its end. A run started while another is going is queued instead of refused, and the job page says where it is in line. Runs that load the same tables never run together.

Refreshed workbench navigation and tab experience

The workbench has a redesigned shell, catalog, admin area, dialogs, and help surfaces built on the shared OpenLegacy kit. The tab workspace now lives under the catalog so users stay in context when opening assets, and each tab has its own close control with clearer loading states. [[product:ol-coreiq|OL CoreIQ]] also m

IBM i data queues can be browsed, classified, and decoded

IBM i data queue endpoints now provide a queue browser, queue viewer, layout attachment, and message classification tools. Operators can load COBOL or PCML layouts, define rules from keys, lengths, or fields inside entries, and see queue entries decoded into the matched layout. [[feature:dataq-support|IBM i data queues

IBM i data queue consumers and queue APIs

Data queues can now be configured as running consumers that decode entries and publish them to webhooks or Kafka with reusable gateway credentials. The same screen can define producer APIs and request-reply queue APIs, publish them through the catalog, and expose them as REST endpoints. [[feature:dataq-support|IBM i da

HTML alert email with a repeating match block

Alert messages can be HTML. One part of the message can repeat for each match, and Preview shows the email before you save the rule.

AtomIQ can run beside OL Hub with Hub sign-in

[[feature:atomiq-hub-on-prem-integration|OL Hub On-Prem Integration]] adds an on-prem deployment path where AtomIQ runs as a container beside OL Hub, supports gateway prefixes, validates Hub identity tokens, and reads licensing from Hub when configured. The header and account experience also align with the OL platform

Workspace AI instructions and a screen tag editor

Each workspace can add instructions that are included in every AI Analysis run. The snapshot viewer can edit form, list, login, and menu tags by picking regions on the screen.

VSAM flows can read full keys and blank key prefixes more efficiently

A VSAM listing step now reads by key when its filter names the complete KSDS key, avoiding a broader gateway filter scan. When the trailing key parts are blank, CoreIQ can use a bounded prefix read and page the results in the workbench. [[feature:vsam-orchestration-flow|VSAM Orchestration Flow]] logs why it used the ke

Published API exposure has safer defaults

Static OpenAPI definitions for VSAM dataset APIs are now hidden unless an administrator explicitly enables them. Swagger lists the dynamic definition by default, and the static endpoints answer as unavailable while the flag is off. [[feature:vsam-dataset-view|VSAM dataset browse, layout, and API]] therefore exposes gen

Fix a failed run from the job page, with AI for the hard cases

When a batch run from CoreIQ (VSAM or IMS) rejects rows, you can now fix its mapping straight from the job page. Tick the causes you want fixed and click Fix in DataIQ. DataIQ opens the mapping editor with the fixes already filled in: allow nulls in a column the source leaves empty, widen a column that's too short for

JCL and data dependency analysis resolves more real-world relationships

[[feature:atomiq-source-analysis-viewers|Source Analysis & Viewers]] now accepts JCL procedure files, uses procedure steps as lookup input, resolves COBOL DD names per job step, and prefers DB tables over same-named files for SQL calls. The resulting graph shows more accurate program-to-dataset, job-to-program, and SQL

Source import handles larger and more realistic source sets

[[feature:atomiq-multi-source-import|Multi-Source Import]] now supports larger multipart uploads, explains the upload limit before submission, accepts identical duplicate files once, and recognizes more PDS copybook patterns. These changes make full application imports and multi-tree source packages easier to stage wit

Terminal MCP sign-in for live host sessions

Live terminal tools moved to /api/v1/mcp/terminal. The [[feature:termiq-mcp-agent-tools|host sign-in]] asks for the workspace, connection, and a sign-on macro or host user and password. Recorded-data tools stay on /api/v1/mcp.

Alert rules on recorded terminal activity

Create alert rules from the same filters you use in reports, schedule how often they run, and email recipient lists when matches appear. Runtime includes an Alerts tab for rules, history, and Run now. Turn on the alert engine and SMTP mail under Account → Settings so deliveries can send. Message templates support built

Localized follow-up suggestions

Follow-up suggestion chips are written in the selected UI language, and the arrow points forward in right-to-left layouts.

Install SOAP services from a WSDL

Add a SOAP service as an application from a WSDL file or URL. When the service exposes more than one port, choose the port before install. You can record HTTP Basic, Bearer, or API key; the secret is entered on Security after install.

Sticky agent editor tabs

Agent sections sit in a sticky, full-width tab bar so the tabs stay in view while you scroll the editor.

Subagents in chat

In Live chat, turn on Subagents so the agent can hand a self-contained task to a helper with a fresh context. Several can run at once, including on a faster model from the same provider. Built-in model pickers also include Claude Haiku 5.5.

New installations include ready-to-explore demo workspaces

[[feature:atomiq-demo-workspaces|Demo Workspaces]] gives new users preloaded mainframe and IBM i examples so they can explore AtomIQ before importing their own sources. The included examples cover CICS insurance, retail banking, and IBM i card management scenarios, with sample operations created after analysis complete

Pull operations from AtomIQ and browse CoreIQ tables from an AI agent

An AI agent can now bring source straight from OL AtomIQ: it lists the connected AtomIQ's workspaces and their operations, sees which ones can be imported and why not, and pulls one live into OL Next, or imports it from an .atq export, then converts it in the same call. The agent never sees an AtomIQ login; it only lea

Agents can discover CoreIQ schemas and tables

The MCP catalog can now drill into CoreIQ data sources to list a connection's schemas and a schema's tables before an agent binds an operation to live data. This helps agents choose real host data names instead of guessing while staying within the guarded [[feature:ol-next-mcp-server|MCP server for AI agents]] workflow

Browse and try your APIs in the console

A new API Docs page in the console sidebar shows the OpenAPI document of your converted flows and RPC programs in Swagger UI, grouped by application and operation. Every Try it out call is sent as the signed-in user, so it works in the hosted console and inside the OpenLegacy Platform, where the API requires sign-in, a

API Docs are available inside the console

OL Next now includes an API Docs page that renders the generated OpenAPI document with Swagger UI inside the signed-in console. Users can browse and try the REST endpoints for flows and RPC programs without leaving [[feature:api-docs|API Docs]].

The App Viewer is easier to navigate at real workspace scale

[[feature:atomiq-interactive-app-viewer|Interactive App Viewer]] adds graph zoom controls, preset zoom stops, full-screen mode, larger graph space, selected-resource arrow filtering, and better dependency visibility while searching. These updates make dense application graphs easier to inspect without losing context or