# OL Edge > Modernize mainframe & legacy systems: expose them as REST, GraphQL, async, and MCP tools. ## Products - [OL Hub](https://edge.web.openlegacy.com/products/ol-hub.md): Govern, deploy, and operate the OpenLegacy suite—SaaS or unified OnPrem—with shared identity, API keys, access control, AI, and MCP. - [OL CoreIQ](https://edge.web.openlegacy.com/products/coreiq.md): Discover, test, and expose mainframe data, files, jobs and programs assets as secure APIs from a single browser-based workbench. - [OL Integration](https://edge.web.openlegacy.com/products/ol-integration.md): Expose mainframe and IBM i business logic as modern APIs without rewriting core systems. - [OL Gene](https://edge.web.openlegacy.com/products/ol-gene.md): Run natural-language agent workflows across APIs and MCP tools from one governed Co-pilot control plane. - [OL AtomIQ](https://edge.web.openlegacy.com/products/ol-atomiq.md): Plan and execute incremental mainframe modernization with visual decomposition and routing. - [OL DataIQ](https://edge.web.openlegacy.com/products/ol-dataiq.md): Query, migrate, and operationalize data across legacy and modern databases. - [OL Spec](https://edge.web.openlegacy.com/products/ol-spec.md): Generate specifications, documentation, and modernization blueprints from legacy systems with AI. - [OL Planner](https://edge.web.openlegacy.com/products/ol-planner.md): Visualize, design, and govern modernization roadmaps with application and architecture planning. - [OL Terminal](https://edge.web.openlegacy.com/products/ol-terminal.md): Give teams instant browser access to 3270 and 5250 terminal screens without desktop emulators—not map descriptors or remote BMS/MFS hosts. - [OL TermIQ](https://edge.web.openlegacy.com/products/ol-termiq.md): Discover business processes and terminal-screen flows from 3270/5250 session recordings with AI-powered analysis—not from BMS/MFS map source. - [OL Next](https://edge.web.openlegacy.com/products/ol-next.md): Convert legacy map-based screen and RPC programs (CICS/BMS, IMS/MFS, RPG/DSPF) into runnable modern code you can validate immediately. The screen player and screen API run maps—not 3270/5250 terminals. - [OL Code](https://edge.web.openlegacy.com/products/ol-code.md): Develop, modernize, and API-enable COBOL and RPG programs in a web IDE. - [OL AppIQ](https://edge.web.openlegacy.com/products/ol-appiq.md): Build enterprise applications, integrations, workflows, and digital experiences with AI-assisted development on OpenLegacy assets. ## Documentation - [Documentation](https://edge.web.openlegacy.com/docs): Product help pages and table of contents ## Features - [Access Control Management](https://edge.web.openlegacy.com/features/platform-access-control.md): Govern who can see and change Hub resources with roles, sharing, request-access workflows, and (planned) custom permission catalogs. - [API Keys Management](https://edge.web.openlegacy.com/features/platform-api-keys.md): Create, revoke, and scope user, account, and runtime API keys for CLI, agents, MCP, and generated services—with short keys that fit host configs. - [Branded App Fallback Pages](https://edge.web.openlegacy.com/features/platform-app-fallback-pages.md): Every platform app tile stays reachable: when a federated app isn't installed or fails to load, the shell renders a branded fallback page instead of a broken route. - [SaaS Platform & Deployment](https://edge.web.openlegacy.com/features/platform-saas-deployment.md): Run the OpenLegacy suite as multi-tenant managed SaaS—sign up, regional tenancy, Auth0 identity, licensing, and cloud deployment out of the box. - [Unified AI and MCP](https://edge.web.openlegacy.com/features/platform-unified-ai-mcp.md): Shared AI service and Model Context Protocol endpoints so assistants and agents use one governed path across Hub and platform products. - [Unified OnPrem Installation](https://edge.web.openlegacy.com/features/platform-unified-onprem.md): Install Hub Enterprise (or Light) once—Keycloak, Postgres, AI, and platform products share one OnPrem stack instead of many siloed installs. - [AS/400 (IBM i) workbench](https://edge.web.openlegacy.com/features/as400-support.md): Explore, operate, and test IBM i (AS/400) systems from OL CoreIQ—SQL, jobs, spools, libraries, program calls, and FTP—in the browser. - [BigID GRA integration (Datasets, IMS-DB, IMS-DLI)](https://edge.web.openlegacy.com/features/bigid-gra-integration.md): Expose CoreIQ mainframe Datasets, IMS-DB (Universal JDBC), and IMS-DLI as BigID Generic REST Adapter (GRA) data sources so BigID can enumerate containers/objects and scan records for classification. - [CICS API bulk creation (Populate from CICS)](https://edge.web.openlegacy.com/features/cics-api-bulk-creation.md): Bulk-discover CICS programs via CMCI from OL-CICS or CTG Browse, match COBOL source and linkage copybooks, add them to the CICS catalog, publish, and expose as REST System APIs with dynamic OpenAPI. - [Dataset CDC](https://edge.web.openlegacy.com/features/dataset-cdc.md): Capture insert, update, and delete changes on VSAM datasets, decode them with catalog layouts, and publish structured events to Kafka or HTTP webhooks from OL CoreIQ. - [DB2 table REST APIs (Populate APIs)](https://edge.web.openlegacy.com/features/db2-table-apis.md): Select DB2 schema tables in Populate APIs, generate CRUD/list/count REST endpoints, publish them from the DB2 catalog, and consume them via dynamic OpenAPI. - [IMS API bulk creation (Populate from IMS)](https://edge.web.openlegacy.com/features/ims-api-bulk-creation.md): Discover IMS transactions from Browse, match COBOL source and DL/I message layouts, publish to the IMS catalog, and expose REST System APIs with OpenAPI. - [IMS-DB table REST APIs (Populate APIs)](https://edge.web.openlegacy.com/features/ims-db-table-apis.md): Select IMS-DB segments in Populate APIs, generate CRUD REST endpoints with JDBC or copybook bodies, publish from the IMS-DB catalog, and consume via OpenAPI. - [IMS-DB Universal JDBC browse, query, and layouts](https://edge.web.openlegacy.com/features/ims-db-jdbc.md): Browse and query IMS databases over Universal JDBC / ODBM, associate COBOL segment layouts into the IMS-DB catalog, and page through segment data from the CoreIQ workbench. - [IMS-DLI native browse, view segments, and layouts](https://edge.web.openlegacy.com/features/ims-dli.md): Browse PSBs and view hierarchical IMS segments via native DL/I batch (OLIMDBR) on z/OS, apply COBOL layouts under the IMS-DLI catalog, and sample/approve segment reachability from CoreIQ. - [VSAM dataset browse, layout, and API](https://edge.web.openlegacy.com/features/vsam-dataset-view.md): Browse and inspect VSAM and other mainframe datasets in the browser, associate COBOL copybooks into a Datasets catalog, and expose published dataset content through CoreIQ REST APIs. - [VSAM records Update](https://edge.web.openlegacy.com/features/vsam-record-cud.md): Insert, update, and delete VSAM KSDS records from CoreIQ View File or host APIs under the caller’s RACF identity—gated by per-endpoint write flags and the dataset-server write surface. - [Asset Management](https://edge.web.openlegacy.com/features/integration-asset-management.md): Discover, version, and test connector assets inside modules—the metadata catalog of legacy operations that methods invoke. - [CLI for Automation](https://edge.web.openlegacy.com/features/integration-cli-automation.md): Automate Hub with the `ol` CLI—create modules, push/pull metadata, test assets, generate services, and deploy from CI/CD. - [Contract-First & Friendly APIs](https://edge.web.openlegacy.com/features/integration-contract-first-ai-apis.md): Define Hub contracts as the API source of truth, then enrich with AI—readable names, descriptions, and specs agents can use. - [Database poller](https://edge.web.openlegacy.com/features/integration-db-poller.md): Poll Oracle, SQL Server, DB2 z/OS, or IBM i DB400 on a schedule, feed each result row into a method flow, and optionally update or clear rows after processing. - [IBM i (AS/400) connectors](https://edge.web.openlegacy.com/features/integration-ibmi-as400-connectors.md): Connect IBM i programs, 5250 screens, data queues, DB2 for i, and JD Edwards functions as APIs—RPC, COBOL, PCML, and DB400. - [IBM i Change Data Capture](https://edge.web.openlegacy.com/features/integration-as400-cdc.md): Capture IBM i (AS/400) DB2 inserts, updates, and deletes from journals and process each change in a Designer method flow—JDBC or RPG fetch, by table or by transaction. - [Mainframe connectors](https://edge.web.openlegacy.com/features/integration-mainframe-connectors.md): Connect IBM Z programs, transactions, data, and 3270 screens as APIs—CICS, IMS, CTG, Natural, VSAM, DB2, and related runtimes. - [Multi-Technology Endpoints](https://edge.web.openlegacy.com/features/integration-multi-technology-endpoints.md): One generic contract, many endpoint styles—OpenAPI, Kafka, Serverless, SOAP, IBM MQ, and more. - [On-prem / legacy on-prem connectors](https://edge.web.openlegacy.com/features/integration-onprem-legacy-connectors.md): Index of OL Integration on-prem connectors: IBM Z, IBM i, SAP/Oracle/SOAP, plus messaging, REST, files, and industry backends. - [On-prem SAP, Oracle, and SOAP connectors](https://edge.web.openlegacy.com/features/integration-onprem-enterprise-connectors.md): Expose SAP BAPIs, Oracle stored procedures, and SOAP services as governed APIs so long-running on-prem systems can serve digital channels and AI agents. - [RPC Flow Methods](https://edge.web.openlegacy.com/features/integration-rpc-flow-methods.md): Orchestrate connector operations—programs, DB calls, SOAP/REST—into typed Hub methods on a visual flow canvas. - [Runtime Dashboards (Grafana)](https://edge.web.openlegacy.com/features/integration-runtime-dashboards-grafana.md): Monitor deployed Hub APIs with Grafana—metrics, logs, and Runtime dashboards scoped by project, tenant, and environment. - [Screens Flow Methods](https://edge.web.openlegacy.com/features/integration-screens-flow-methods.md): Automate 3270/5250 terminal-screen journeys as Hub methods with screen invoke, conditions, trail-based generation, and reusable terminal-screen subflows. This is terminal (3270/5250) automation—not BMS/MFS map APIs. - [Test Center](https://edge.web.openlegacy.com/features/integration-test-center.md): Build and run ordered test plans from Hub flow test cases—with history, streaming results, and CLI/CI execution. - [Agent Builder](https://edge.web.openlegacy.com/features/ol-gene-agent-builder.md): OL Gene Agent Builder creates role-based agents through a guided chat flow—with sidebar access, required instructions, and skill proposals. - [Agents](https://edge.web.openlegacy.com/features/ol-gene-agents.md): OL Gene Agents package instructions, tools, skills, context, workflows, and generative UI into assistants runnable in Co-pilot or as MCP endpoints. - [Applications and OpenAPI Integrations](https://edge.web.openlegacy.com/features/ol-gene-applications-openapi.md): OL Gene turns OpenAPI specs and Postman collections into agent-ready applications with org or per-user auth, operation filters, and generated MCP tools. - [Audit Logs](https://edge.web.openlegacy.com/features/ol-gene-audit-logs.md): OL Gene Audit Logs track configuration changes—apps, agents, settings, and API tokens—for compliance and change control. - [Context](https://edge.web.openlegacy.com/features/ol-gene-context.md): OL Gene Context stores reusable knowledge that chats and agents can mention or attach for consistent answers and policies. - [Context Types](https://edge.web.openlegacy.com/features/ol-gene-context-types.md): OL Gene Context Types define reusable schemas for context items so knowledge stays structured and discoverable across agents. - [Co-pilot Chat](https://edge.web.openlegacy.com/features/ol-gene-copilot-chat.md): OL Gene Co-pilot runs natural-language workflows across APIs and agents in one chat—with drag-and-drop files, pinned threads, and live tool execution. - [Insights](https://edge.web.openlegacy.com/features/ol-gene-insights.md): OL Gene Insights is the organization analytics hub for conversations, agents, workflows, and actions—with LLM cost estimates and chart export. - [Interaction Recording Controls](https://edge.web.openlegacy.com/features/ol-gene-interaction-recording.md): OL Gene Interaction Recording lets admins choose full, headers-only, or disabled storage of request and response bodies in Actions. - [MCP Gateway](https://edge.web.openlegacy.com/features/ol-gene-mcp-gateway.md): OL Gene MCP Gateway exposes apps and agents as remote MCP endpoints—with workflow tools, parallel runs, and OAuth or API-key auth. - [Native MCP Servers](https://edge.web.openlegacy.com/features/ol-gene-native-mcp-servers.md): OL Gene connects official, registry, and custom native MCP servers so agents can use external MCP tools alongside OpenAPI apps. - [Organization Advanced Controls](https://edge.web.openlegacy.com/features/ol-gene-org-advanced-controls.md): OL Gene organization settings control egress proxy, model visibility, recording policies, response limits, caching, PII sanitization, mock execution, and branding. - [Postman Collection Import](https://edge.web.openlegacy.com/features/ol-gene-postman-import.md): OL Gene imports Postman collections, converts them to OpenAPI, and installs them as applications with generated MCP tools. - [Skills](https://edge.web.openlegacy.com/features/ol-gene-skills.md): OL Gene Skills are reusable Agent Skills packages that teach agents consistent procedures across Co-pilot and MCP clients. - [Tasks](https://edge.web.openlegacy.com/features/ol-gene-tasks.md): OL Gene Tasks save prompts with a model and optional agent, then run them on demand or on a daily/weekly schedule from Co-pilot. - [Token Optimization and Context Efficiency](https://edge.web.openlegacy.com/features/ol-gene-token-optimization-context-efficiency.md): Reduce agent token cost and latency with dynamic tool loading, response projection, and optional JSON Compact or TOON compression. - [Workflows](https://edge.web.openlegacy.com/features/ol-gene-workflows.md): OL Gene Workflows are multi-step agent graphs with branching, LLM steps, human approvals, dry-run simulation, and MCP authoring for deterministic automation. - [AS/400 (IBM i) & RPG](https://edge.web.openlegacy.com/features/atomiq-as400-rpg-support.md): Run AtomIQ as a first-class IBM i platform: JT400 import, DB400, DSPF map preview, and RPG analysis pipeline alongside COBOL. - [Data Lineage](https://edge.web.openlegacy.com/features/atomiq-data-lineage.md): Trace data from DB2 columns, IMS segments, and file fields through COBOL host variables across programs and copybooks. - [Graph Assistant & MCP](https://edge.web.openlegacy.com/features/atomiq-graph-assistant-mcp.md): In-app graph-aware AI chat plus a built-in MCP server so assistants can read and drive AtomIQ workspaces programmatically. - [IMS COBOL and MFS maps](https://edge.web.openlegacy.com/features/atomiq-ims-mfs-support.md): Analyze IMS-DC COBOL and MFS maps in AtomIQ: preview device formats, classify CBLTDLI screen vs segment calls, and walk conversational UI flow from source. - [Interactive App Viewer](https://edge.web.openlegacy.com/features/atomiq-interactive-app-viewer.md): Drag-and-drop canvas to organize programs into apps by business usage, visualize dependencies, filter, and persist workspaces. - [Map UI analysis → Hub terminal Screens Flow](https://edge.web.openlegacy.com/features/atomiq-screen-flow-code-first.md): From COBOL plus BMS or MFS maps, analyze the UI state machine in source. For CICS + BMS, build an OL Integration terminal Screens Flow. AtomIQ shows maps and analyzes source; it does not run a live terminal. - [Modernization Rules & Routing](https://edge.web.openlegacy.com/features/atomiq-modernization-routing.md): Apply modernization/decoupling rules and manage gateway route lifecycle—register, approve, publish, and unpublish cross-app dependencies. - [Multi-Source Import](https://edge.web.openlegacy.com/features/atomiq-multi-source-import.md): Import mainframe and IBM i assets into AtomIQ from RSE, JZOS, CICS CMCI, Hub Planner, CoreIQ, JT400, or file upload. - [Operations & Domain Classification](https://edge.web.openlegacy.com/features/atomiq-operations-domain-classification.md): Identify and save operations, suggest domains from operation groups, and decouple apps along business process boundaries. - [Source Analysis & Viewers](https://edge.web.openlegacy.com/features/atomiq-source-analysis-viewers.md): Inspect COBOL and related source with AI documentation, BMS/DSPF/MFS map preview, DB2 table metadata, and file layout resolution. Map preview renders map definitions—not live 3270/5250 terminal screens. - [AI Query Assistant](https://edge.web.openlegacy.com/features/dataiq-ai-query-assistant.md): Natural-language chat that generates and refines SQL from live schema context and can explain query or stored-procedure errors. - [Import and export test data and schema](https://edge.web.openlegacy.com/features/dataiq-import-export-test-data-schema.md): Move schemas and query result datasets between connections, export/import connection configs, and download CSV—so teams can build and refresh realistic test environments quickly. - [VSAM batch data migration](https://edge.web.openlegacy.com/features/dataiq-vsam-batch-data-migration.md): Export CoreIQ mapping packs as .odz, run Spring Batch jobs that load VSAM datasets into SQL tables, and monitor execution from a bundled Batch dashboard. - [VSAM schema migration from CoreIQ](https://edge.web.openlegacy.com/features/dataiq-vsam-schema-migration.md): Browse CoreIQ VSAM/KSDS layouts, generate CREATE TABLE DDL with copybook-aware column mapping, and persist field-to-column lineage per database connection. - [AI Spec Generator Chat](https://edge.web.openlegacy.com/features/olspec-ai-spec-chat.md): Author and refine business process specifications in a threaded AI chat with open questions, reference-file context, and one-click finalization. - [API Integration Points Wizard](https://edge.web.openlegacy.com/features/olspec-api-integration-points.md): Capture modernization intent (UI / Logic / Data / Files / Batch) and select AtomIQ resources as API boundary candidates from a persisted snapshot. - [AtomIQ / Code Base Import](https://edge.web.openlegacy.com/features/olspec-atomiq-import.md): Build specifications by selecting AtomIQ operations live or from a `.atq` export, with streaming generation and optional reference-file context. - [Business Process Spec Authoring](https://edge.web.openlegacy.com/features/olspec-bp-spec-authoring.md): Edit full specifications and operations with markdown, AI enhance, import diffs, model cards, and PDF/Word export. - [Operation & App Players](https://edge.web.openlegacy.com/features/olspec-operation-players.md): Play UI flows and service operations in-browser—per operation or from a workspace-wide App Player—including optional 3270 terminal mode for legacy workspaces. - [Plugins & Codegen](https://edge.web.openlegacy.com/features/olspec-plugins-codegen.md): Extend workspaces with codegen and scaffolding plugins—setup, workspace builds, and per-operation Execute with downloadable artifacts. - [Process Versioning & Compare](https://edge.web.openlegacy.com/features/olspec-process-versioning.md): Work on a live Draft, freeze numbered snapshots (v1, v2, …), and compare any two versions side by side. - [Runnable Artifact Generation](https://edge.web.openlegacy.com/features/olspec-runnable-artifacts.md): Generate per-operation UI models, process logic specs, Groovy controllers, and sample data as playable artifacts. - [Shared Business Models](https://edge.web.openlegacy.com/features/olspec-business-models.md): Capture workspace-scoped data models shared across operations, with I/O roles, CRUD usage, and navigable cross-references. - [Workspace Roles Catalog](https://edge.web.openlegacy.com/features/olspec-workspace-roles.md): Auto-collect actor and responsibility roles from specifications and show primary / secondary involvement on each operation. - [Admin User Management](https://edge.web.openlegacy.com/features/admin-user-management.md): Provision managed terminal users in admin, map external JWT launch identity to device and session settings, and apply them before the host session opens. - [AS/400 printer and spool integration](https://edge.web.openlegacy.com/features/as400-printer-integration.md): Browse, filter, preview, download as PDF, and delete AS/400 spooled files from the terminal UI after 5250 login. - [Browser-based 3270 and 5250 emulation](https://edge.web.openlegacy.com/features/browser-3270-5250-emulation.md): Connect to IBM Z and IBM i applications from any modern browser—full 3270/5250 terminal field editing, function keys, and keyboard mappings without desktop emulators. Not a map player. - [Centralized session admin and recording](https://edge.web.openlegacy.com/features/centralized-session-admin.md): Admin panel for connectivity settings, key mappings, live session monitoring, recorded trails, homepage branding, and secure deployment. - [Hub screen flow player and debugger](https://edge.web.openlegacy.com/features/hub-screen-flow-player-debugger.md): Run and step-debug Hub terminal Screens Flows against a live 3270/5250 session from the OL Terminal Play Flow panel. - [Macro recording and playback](https://edge.web.openlegacy.com/features/macro-recording-playback.md): Record keystroke sequences and replay them at high speed with action-aware pauses—automate login and repetitive terminal navigation. - [Type-ahead keystroke queue](https://edge.web.openlegacy.com/features/type-ahead-keystroke-queue.md): Keep typing while the host processes Enter and function keys—keystrokes queue in order and drain when the session unlocks. - [AI flow analysis → Hub artifacts](https://edge.web.openlegacy.com/features/termiq-hub-flow-creation.md): Select completed operation instances, run AI happy-path analysis over terminal events, and create Hub terminal Screens Flow artifacts (project/module/method/contract/trail) for OL Integration—3270/5250 green-screen APIs, not map ScreenFlows. - [AI screen identification & merge](https://edge.web.openlegacy.com/features/termiq-ai-screen-identification.md): Run LLM screen naming/description over multi-snapshot dynamism only after privacy sanitization masks per-session data (letters→X, digits→9)—raw buffers stay local—then merge duplicate screens by catalog name, identifiers, or structural fingerprint with event repointing. - [Operation definitions (identify business operations)](https://edge.web.openlegacy.com/features/termiq-operation-definitions.md): Author named business operations with start, end, and reset triggers—screen, action, and field conditions—so TermIQ can identify workflows inside recorded terminal event streams. - [Operation instance collection](https://edge.web.openlegacy.com/features/termiq-operation-instances.md): Durably track active and completed operation instances as terminal events match operation-definition triggers—in real time during ingest or via retroactive backfill—with duration, steps, and linked event detail. - [Runtime reporting & dashboard](https://edge.web.openlegacy.com/features/termiq-runtime-reporting.md): Run builtin (predefined) and custom workspace reports over Events, Operations, and Sessions—with primary/additional filters, group-by charts (pie/bar/line/doughnut), rolling or fixed date ranges, drill-down, Excel export, and a pin-to-dashboard experience for operation/session health. - [Session and trail viewing](https://edge.web.openlegacy.com/features/termiq-session-trail-viewing.md): Replay recorded workspace sessions and preview trail files step-by-step with ACTION highlighting, thumbnail navigation, and start/end markers to draft operation definitions from real journeys. - [Terminal event recording (webhook & trails)](https://edge.web.openlegacy.com/features/termiq-terminal-event-recording.md): Ingest live OL Terminal webhook traffic or batch trail uploads into a shared analyzer pipeline that discovers screens, persists snapshots, and writes terminal events—then analyze them in Runtime → Events with session/user/date filters, source-snapshot dimensions (screen, operation, state, action, global model, tags), configurable columns, group-by, selection for operation definitions, and CSV export. - [Workspace screen discovery & model mapping](https://edge.web.openlegacy.com/features/termiq-workspace-screen-discovery.md): Curate a workspace screen catalog from recorded snapshots—name, tag, publish, compare, sanitize, map fields to Hub global models, and optionally attach BMS/DDS/DSP screen maps. - [CICS COBOL / BMS migration](https://edge.web.openlegacy.com/features/cics-cobol-bms-migration.md): Convert CICS COBOL screen programs with BMS maps into runnable legacy code on the JVM you can play in OL Next—map player, not a 3270 terminal. - [DB access management](https://edge.web.openlegacy.com/features/db-access-management.md): Point replatformed programs at an H2 sandbox (schema.sql / seed.sql), a live host store (DB2, VSAM, IMS-DB via JDBC or CoreIQ APIs), or a modern DB after data migration—so logic can leave the host before data does. - [IMS COBOL / MFS migration](https://edge.web.openlegacy.com/features/ims-cobol-mfs-migration.md): Convert IMS DC COBOL programs with MFS maps into runnable legacy code on the JVM you can play and validate in OL Next—MFS map conversations, not 3270. - [Interactive program player](https://edge.web.openlegacy.com/features/interactive-program-player.md): Run converted map-based screen programs in the browser—map-layout grid, AID keys, and run log—with no mainframe and no 3270/5250 terminal session. - [Map screen flows](https://edge.web.openlegacy.com/features/map-screen-flows.md): Author map ScreenFlows with explicit I/O, expose via OpenAPI, and record/run/debug against converted map programs—not Hub terminal Screens Flows. - [RPC input / output](https://edge.web.openlegacy.com/features/rpc-input-output.md): Invoke converted COBOL and RPGLE RPC procedures with typed commarea input and output forms—edit the schema, call, and inspect results. - [RPG / DSPF migration](https://edge.web.openlegacy.com/features/rpg-dspf-migration.md): Convert RPGLE screen programs with DSPF maps (and RPGLE RPC modules) into runnable legacy code on the JVM through the OL Next RPG kits—DSPF maps, not 5250 terminal emulation. - [Hub asset testing from the IDE](https://edge.web.openlegacy.com/features/hub-asset-testing.md): Create Hub modules/assets from open COBOL and run JSON test cases against Hub directly in the Code Viewer—validate legacy logic before and after API enablement. - [Legacy explorer and code editor](https://edge.web.openlegacy.com/features/legacy-explorer-code-editor.md): Browse Mainframe and IBM i datasets in a web explorer, then view, edit, compile, and navigate COBOL/RPG with a multi-tab code editor. - [Reverse API client generation](https://edge.web.openlegacy.com/features/reverse-api-client.md): Generate COBOL/RPG clients from Hub REVERSE projects or OpenAPI specs so legacy programs can call modern HTTP APIs via OLREVAPI. - [Screen to RPC conversion](https://edge.web.openlegacy.com/features/screen-to-rpc.md): Convert Mainframe screen COBOL into RPC-style programs that preserve business rules—ready to expose as Hub APIs and modern services. - [AI Spec Generation](https://edge.web.openlegacy.com/features/appiq-ai-spec-generation.md): Generate UI specs, data models, and OpenAPI from Trail AI analysis or Markdown process specs written in the Process Designer Spec tab. - [Global Models & CRUD Process Wizards](https://edge.web.openlegacy.com/features/appiq-global-models-crud.md): Define shared global models, then generate linked List / Get / Create / Update / Delete processes with searchable fields, columns, and form display modes. - [Industry Process Templates](https://edge.web.openlegacy.com/features/appiq-industry-templates.md): Bootstrap processes from industry → category → business-process templates (e.g. Banking, Insurance, Healthcare) that generate UI specs, OpenAPI, models, and docs. - [Manage APIs & Hub Publishing](https://edge.web.openlegacy.com/features/appiq-manage-apis-hub-publish.md): Browse application operations, upload OpenAPI, publish methods/contracts to OL Hub / OL Integration, and track deployment status. - [Multi-Environment Deployment Profiles](https://edge.web.openlegacy.com/features/appiq-deployment-profiles.md): Configure dev/test/prod profiles with separate Hub connections, auth, and endpoints; switch environments and publish safely. - [OAuth2 with AS/400 & Mainframe Providers](https://edge.web.openlegacy.com/features/appiq-oauth2-legacy-auth.md): Secure modern apps with OAuth2/JWT and pluggable providers—AS/400, mainframe (RSE), and mock—for legacy-credential login. - [OpenAPI Providers & API Testing](https://edge.web.openlegacy.com/features/appiq-openapi-providers-testing.md): Wire MOCK, OL Hub, or external OpenAPI providers, and test endpoints in-product with request/response inspection. - [Process Designer (UI, OpenAPI, Models, Docs)](https://edge.web.openlegacy.com/features/appiq-process-designer.md): Design and maintain each process’s modern UI (jsonSpec), OpenAPI 3.0, normalized models, mock data, and Markdown documentation in one designer. - [Screen & TermIQ Process Import](https://edge.web.openlegacy.com/features/appiq-screen-termiq-import.md): Import terminal processes from .trail recordings or OL TermIQ .trmiq files (and screen maps) into AppIQ processes with UI, OpenAPI, models, mock data, and docs. - [Theme Management](https://edge.web.openlegacy.com/features/appiq-theme-management.md): Create and manage per-application UI themes—CSS editing, preview, default/active lifecycle, duplicate, and image assets—so generated apps match brand guidelines. ## Capabilities - [API Integration](https://edge.web.openlegacy.com/capabilities/api-integration.md): Ship governed APIs and events from mainframe and IBM i assets faster than custom connector builds or general-purpose integration platforms, with repeatable design, test, and runtime operations across OL Integration (terminal Screens Flows and asset management), OL Screener (map ScreenFlows), OL DataIQ (DB system APIs), and OL Code — building on OL Hub's shared discovery and specification work instead of starting each integration from zero. - [AS/400 (IBM i) Modernization](https://edge.web.openlegacy.com/capabilities/as400-ibmi-modernization.md): Give IBM i shops a single modernization path—from day-one browser access and green-screen operations through RPG/DSPF analysis, RPC conversion, governed APIs, and OAuth2-secured modern front ends—without stitching together point tools across OL CoreIQ, OL Terminal, OL Code, OL AtomIQ, OL Next, OL AppIQ, OL DataIQ, and OL Integration, or re-inventorying the same RPG and DSPF assets each time OL Hub adds a new capability. - [Code Replatforming](https://edge.web.openlegacy.com/capabilities/code-replatforming.md): Lower-risk incremental replatform versus full rewrite: keep editing the legacy programs in OL Next, run them off the host, and move data when the business is ready—sandbox, live DB2/VSAM/IMS-DB, or a modern store. - [Legacy Code Analysis](https://edge.web.openlegacy.com/capabilities/legacy-code-analysis.md): Replace tribal knowledge with inspectable inventory, operations, and lineage before API, coexistence, or replatform work starts—using OL AtomIQ, OL TermIQ, and OL Code together. - [Legacy Data APIs](https://edge.web.openlegacy.com/capabilities/legacy-data-apis.md): Give developers and agents governed data access without green-screen extracts or one-off host jobs—via OL CoreIQ, OL DataIQ, and OL Z Gateway. - [Legacy Data Synchronization](https://edge.web.openlegacy.com/capabilities/legacy-data-synchronization.md): Enable near-real-time or scheduled replication without custom CDC/polling frameworks on the host—combining CoreIQ CDC, Z Gateway hosting, and DataIQ Hub poller/ETL/migration. - [Legacy–Modern Coexistence](https://edge.web.openlegacy.com/capabilities/legacy-modern-coexistence.md): Modernize incrementally—expose System APIs outbound and Reverse APIs inbound—without a big-bang cutover, using OL Integration, OL CoreIQ, OL Code, and OL AtomIQ. - [Reverse Engineering & Business Specs](https://edge.web.openlegacy.com/capabilities/reverse-engineering-business-specs.md): Produce reviewable business specs and modernization blueprints from real code and usage—not blank-page documentation—led by OL Spec with AtomIQ and TermIQ inputs. - [Token Optimization and Context Efficiency](https://edge.web.openlegacy.com/capabilities/token-optimization-context-efficiency.md): Lower LLM input cost and response time by sending agents only the schemas and data they need, while preserving governed access to enterprise APIs. - [Unstructured legacy data access/migration](https://edge.web.openlegacy.com/capabilities/unstructured-legacy-data-access-migration-mso428l9.md): Modernization and integration teams gain a governed path to discover, understand, access, update, stream, and migrate legacy IMS-DB and VSAM data using approved layouts and shared catalog definitions. This reduces reliance on green-screen tools, custom extract jobs, hand-written DDL, and disconnected lineage tracking while enabling APIs, event pipelines, and SQL migration targets from trusted mainframe data structures. ## Case studies - [Monprix goes live](https://edge.web.openlegacy.com/case-studies/monprix-goes-live-mspxf62c.md): Monoprix ## Blog (latest published) - [Modernize Banking and Financial Services Without Disruption](https://edge.web.openlegacy.com/blog/financial-services-modernization.md): Open Banking, real-time payments, and AI-driven fraud detection all need the same thing: fast, governed access to what's already running on the mainframe or IBM i — not a rip-and-replace program. (2026-08-27) - [The OL Hub Platform: Modernize Without Risk, At Your Pace](https://edge.web.openlegacy.com/blog/ol-hub-platform-overview.md): Legacy modernization fails when it's one big rewrite or a single black-box tool. OL Hub is neither — it's the control plane for a real product suite that discovers, blueprints, and ships modernization work in phases. (2026-08-20) - [Integration Is a Flavor of Modernization](https://edge.web.openlegacy.com/blog/integration-is-a-flavor-of-modernization.md): API integration gets treated as the thing you do while you plan the "real" rewrite. Gartner's own modernization framework disagrees — and agentic AI just made Encapsulate urgent, not optional. (2026-08-17) - [Can Legacy VSAM Data Power AI Initiatives Without a Full Migration?](https://edge.web.openlegacy.com/blog/legacy-vsam-data-ai-initiatives-without-migration.md): VSAM files and COBOL copybooks don't have to block AI adoption. Learn how banks and insurers can augment legacy mainframe data for RAG and AI — without migration risk. (2026-08-11) - [Welcome to OL Edge](https://edge.web.openlegacy.com/blog/welcome-to-ol-edge.md): One place to find every OpenLegacy product, capability, and modernization scenario — for the humans who read it and the agents who query it. Here's your guided tour. (2026-08-08) - [Buy vs. Build](https://edge.web.openlegacy.com/blog/buy-vs-build-msft18qq.md): Buying a proven API integration solution helps teams expose mainframe and IBM i business logic faster, with less custom code, less datatype risk, and more repea… (2026-08-06) ## Resources - [Resources](https://edge.web.openlegacy.com/resources) - [Customer Case Studies](https://edge.web.openlegacy.com/resources/case-studies) - [Customer Case Studies (alias)](https://edge.web.openlegacy.com/case-studies) - [Briefs & Datasheets](https://edge.web.openlegacy.com/resources/briefs) - [eBooks, Reports & Whitepapers](https://edge.web.openlegacy.com/resources/ebooks) - [Videos & Webcasts](https://edge.web.openlegacy.com/resources/videos) - [Blog](https://edge.web.openlegacy.com/resources/blog) - [Blog (alias)](https://edge.web.openlegacy.com/blog) - [Demo Center](https://edge.web.openlegacy.com/resources/demos) ## FAQ - [FAQ](https://edge.web.openlegacy.com/faq) - [How do I get, extend, or apply a Hub or runtime license?](https://edge.web.openlegacy.com/faq/how-to-get-extend-apply-hub-license) - [How do I add users or change Hub roles?](https://edge.web.openlegacy.com/faq/how-to-add-users-and-hub-roles) - [Why can't I log in to Hub, CLI, or the download site?](https://edge.web.openlegacy.com/faq/cannot-login-hub-cli-sso) - [Can OpenLegacy support Adabas environments?](https://edge.web.openlegacy.com/faq/openlegacy-support-adabas-environments) - [How do I set up or debug a Hub connector (IMS, DB2, Kafka, JDBC, SOAP, MQ)?](https://edge.web.openlegacy.com/faq/how-to-setup-debug-hub-connector) - [How do I map fields between expression, invocation, and output steps?](https://edge.web.openlegacy.com/faq/how-to-map-expression-flow-fields) - [How do I add an IBM i (AS/400) asset from PCML or by browsing the backend?](https://edge.web.openlegacy.com/faq/how-to-add-as400-pcml-asset) - [How do I record and replay macros, and why do they fail after a screen layout change?](https://edge.web.openlegacy.com/faq/terminal-record-replay-macros) - [How do I deploy a generated service and connect to it from Hub?](https://edge.web.openlegacy.com/faq/how-to-deploy-and-connect-generated-service) - [How do I preview and download AS/400 spool files as PDF from the browser session?](https://edge.web.openlegacy.com/faq/terminal-as400-spool-pdf) - [Why can't the CLI push an asset, generate, or export an OPZ?](https://edge.web.openlegacy.com/faq/cli-push-generate-export-opz-fails) - [How do managed users and JWT launch assign a 5250 device name before the host session opens?](https://edge.web.openlegacy.com/faq/terminal-jwt-5250-device-name) - [How do I capture terminal events — live webhook from OL Terminal versus trail upload?](https://edge.web.openlegacy.com/faq/termiq-webhook-vs-trail-upload) - [Why does AI screen identification mask values before calling the model?](https://edge.web.openlegacy.com/faq/termiq-why-ai-masks-before-llm) - [Why is the agent aimed at regulated industries?](https://edge.web.openlegacy.com/faq/aws-atx-regulated-industries) - [How do I define start, end, and reset triggers so operation instances actually collect?](https://edge.web.openlegacy.com/faq/termiq-start-end-reset-triggers) - [How do I convert IMS COBOL + MFS, and when do I pass PSB and DBD?](https://edge.web.openlegacy.com/faq/next-ims-cobol-mfs-psb-dbd) - [How does Hub on AWS / Marketplace relate to this agent?](https://edge.web.openlegacy.com/faq/aws-atx-hub-on-aws-marketplace) - [How do I convert RPGLE + DSPF maps versus an RPGLE RPC module?](https://edge.web.openlegacy.com/faq/next-rpgle-dspf-vs-rpc) - [What does the agent do inside an AWS Transform job at the decomposition step?](https://edge.web.openlegacy.com/faq/aws-atx-agent-at-decomposition) - [How does coexistence keep a workload on AWS talking to systems still on the mainframe?](https://edge.web.openlegacy.com/faq/aws-atx-coexistence-bridges) - [What is in beta today versus still missing from the catalog?](https://edge.web.openlegacy.com/faq/aws-atx-beta-vs-missing-catalog) - [How do I invoke a converted COBOL or RPGLE RPC procedure?](https://edge.web.openlegacy.com/faq/next-rpc-player-invoke-procedure) - [Which ol-refactor source kit should I pass on the CLI?](https://edge.web.openlegacy.com/faq/next-ol-refactor-source-kits) - [How do I generate a COBOL or RPG Reverse API client from Hub versus OpenAPI?](https://edge.web.openlegacy.com/faq/code-reverse-client-hub-vs-openapi) - [How do I search datasets by name versus content, and mark My Maps or My Copybooks?](https://edge.web.openlegacy.com/faq/code-search-name-content-my-maps) - [How do I convert a screen COBOL program to RPC — algorithm versus AI-assisted?](https://edge.web.openlegacy.com/faq/code-screen-cobol-to-rpc) - [How do I create a Hub asset from the open COBOL program and run JSON tests in the IDE?](https://edge.web.openlegacy.com/faq/code-hub-asset-from-open-cobol) - [How do I create a Hub asset from COBOL copybooks?](https://edge.web.openlegacy.com/faq/how-to-create-asset-from-copybooks) - [When is Git available in OL Code, and why did pull/push ask for a token?](https://edge.web.openlegacy.com/faq/code-git-available-token-prompt) ## Machine-readable feeds - [Blog RSS 2.0](https://edge.web.openlegacy.com/blog/feed.xml) - [Blog Atom](https://edge.web.openlegacy.com/blog/feed.atom) - [MCP Server (public, no auth)](https://edge.web.openlegacy.com/mcp-public) - [MCP Server (sales)](https://edge.web.openlegacy.com/mcp-sales) - [MCP Server (marketing)](https://edge.web.openlegacy.com/mcp-marketing) - [MCP Server (rnd)](https://edge.web.openlegacy.com/mcp-rnd) - [MCP Server (editor)](https://edge.web.openlegacy.com/mcp-editor) - [MCP Server (employee / browse)](https://edge.web.openlegacy.com/mcp-employee) ## Conventions - Append `.md` to any `/products|features|capabilities|case-studies|blog/` URL for raw markdown. - Those markdown documents include public screenshots and cover/logo stills as `![alt](absolute /media/… URL)`. - Append `?format=md` for the same content. - Case study full-page HTML: `/cs/` (also listed in sitemap). - Resource hubs: `/resources/`; generic resource items: `/resources//`. - FAQ: `/faq` and `/faq/`. - Discovery: `/llms.txt`, `/sitemap.xml`, `/robots.txt`. - MCP help tools: `get_edge_help` (/mcp-public), `get_sales_help`, `get_marketing_help`, `get_rnd_help`, `get_editor_help`, `get_employee_help` on the matching persona paths.