OL DataIQ · Legacy and modern data
Your legacy data to SQL, APIs, and agents
One browser workspace for DB2, DB2 for i, IMS DB, Oracle, SQL Server, PostgreSQL, MySQL, and MongoDB. Query with AI help, migrate VSAM and IMS data into SQL, and publish queries, stored procedures, and tables as data APIs that applications and AI agents can use.
How it works
From mainframe data to governed data APIs, in one workspace
01Connect and explore
Every database in one catalog
Connect once to legacy and modern databases, browse schemas, keys, and stored procedures, see relationships on a graph, and query with schema-aware autocomplete or plain-language AI help.
02Migrate
VSAM and IMS into SQL
Read record layouts from the OL CoreIQ catalog, generate CREATE TABLE DDL with copybook-aware mapping, and load the data with a batch job that shows why rows were refused so you can fix the mapping and rerun.
03Expose
Queries become APIs
Publish a query, a stored procedure, or a table's CRUD operations as an HTTP API with typed parameters and an OpenAPI document, or hand a query to OL Integration as an API, ETL flow, or DB poller.
Key features
Everything a data team needs across legacy and modern databases
01 / CONNECTIONS
Multi-database catalog
DB2, DB2 for i, IMS DB, Oracle, SQL Server, PostgreSQL, MySQL, and generic JDBC in one catalog, with passwords encrypted at rest.
02 / CONSOLE
SQL Query Console
Autocomplete, run a selection, sort and filter results, edit cells, generate UPDATE and DELETE from primary keys, keep history, and export CSV.
03 / AI
AI Query Assistant
Ask in plain language and get SQL written from the live schema. Ask why a query or stored procedure failed and get an explanation.
04 / SCHEMA
Browse and edit schemas
Tables, keys, indexes, and procedures, a foreign-key graph, visual Create and Alter Table designers, and a procedure editor for DB2 and DB2 for i.
05 / MIGRATION
VSAM and IMS to SQL
Copybook-aware DDL that handles REDEFINES, OCCURS, and key inference, with field-to-column lineage kept for each connection.
06 / BATCH
Batch loads you can fix
Load VSAM datasets and IMS segments with a batch job, see why rows were refused, fix the mapping, and rerun to load the rest.
07 / DATA APIS
Queries, procedures, and tables as APIs
Typed parameters from the database catalog, an OpenAPI document for each API, and API-key access for applications and agents.
08 / TEST DATA
Build test environments
Copy table structures and filtered query results between connections, share connection sets as JSON, and export results as CSV.
Video / Data APIs
Publish queries, stored procedures, and tables as data APIs
On an Oracle connection, a query is written and run in the console, and Create API turns its fixed value into a parameter. A stored procedure is published with parameters read from the database catalog, and a table becomes list, get, create, update, and delete APIs. The Data APIs page lists every published API with its OpenAPI documentation, and Try it out calls one live.
Mainframe data migration
Move VSAM and IMS data into SQL, with the mapping you can see
DataIQ reads VSAM KSDS and IMS-DB segment layouts from the OL CoreIQ catalog and generates CREATE TABLE DDL with copybook-aware column mapping. Mappings package into a portable pack, and a batch service loads the records from the CLI or over HTTP, with each run on a batch dashboard.
Know why it was slow
Read metrics that explain every load
See throughput, time spent waiting on the host, page latency, and cost per page as the scan advances, along with the paging settings that move those numbers. Export the results as Markdown or self-contained HTML reports. This capability is in beta.
Video / IMS to SQL
Import an IMS-DB schema and load PostgreSQL
OL CoreIQ runs a read-only query against IMS-DB. In OL DataIQ, Import Legacy Schema picks the CoreIQ connection and the IMS-DB catalog and maps the segments into a PostgreSQL database. After the schema is created, a batch job loads the customer segment rows, and the console shows the populated tables.
AI and MCP
Agents query data without seeing credentials
DataIQ connections are exposed over MCP, so an AI agent can list collections, sample schemas, and run queries through the stored connection without a credential passing through the prompt. Over the same MCP server, an agent can describe a stored procedure, publish it or a query as a data API, and invoke, update, or delete that API.
Part of the platform
Pipelines and integration, one click away
From a working SELECT, create a query in a new or existing OL Integration API project or DB module. From query results, create ETL flows between connections, or DB Poller projects that watch Oracle, SQL Server, DB2, or DB2 for i for changes.
Video / MongoDB
NoSQL in the same workspace
A MongoDB connection is added next to existing SQL and JDBC connections, with its connection string, auth database, and default database. The explorer opens a customers collection, a FIND runs with a limit, and the results appear as both a table and documents.
At a glance
One workspace instead of a tool per database
Database engines
DB2, DB2 for i, IMS DB, Oracle, SQL Server, PostgreSQL, MySQL, and MongoDB, plus generic JDBC.
Ways to publish a data API
From a query, a stored procedure, or a table's CRUD operations.
Mainframe sources migrated to SQL
VSAM datasets and IMS-DB segments, from CoreIQ layouts.
Credentials in the prompt
Agents work through stored connections over MCP.
ECOSYSTEM
Works with the databases you already run
Legacy and modern engines side by side, connected to the rest of the OpenLegacy platform.
FAQ
Common questions
Which databases does OL DataIQ support?
DB2 on z/OS, DB2 for i, IMS DB, Oracle, SQL Server, PostgreSQL, MySQL, MongoDB, and any source with a JDBC driver.
How does VSAM and IMS migration work?
DataIQ reads the record layouts from the OL CoreIQ catalog, generates CREATE TABLE DDL with copybook-aware mapping, and loads the data with a batch service. Refused rows are reported with their cause, so you can fix the mapping and rerun.
Can AI agents use DataIQ?
Yes. DataIQ exposes an MCP server, so agents can explore schemas, run queries through stored connections, and publish or invoke data APIs without seeing credentials. OL Gene uses it to build data system APIs for governed workflows.
How are passwords protected?
Connection passwords are encrypted at rest, and published data APIs are accessed with API keys.
Put your legacy data to work
Tell us which databases and mainframe files you want to query, migrate, or expose as APIs, and we will set up a working demo.
Thanks — we received your message.
Something went wrong. Please try again.