IMS Data Access
IMS Data Access
CoreIQ supports two IMS data paths.
IMS-DB
Use IMS-DB endpoints to query IMS databases, page through results, retrieve metadata, and associate copybooks to interpret segment data. Set Limit and use Prev and Next for cursor-based paging. Layout associations are saved in the IMS-DB catalog.
Open IMS-DB → Browse to list schemas (PCBs) and click Populate APIs to create table REST APIs (CRUD, list, count). The dialog matches DB2 Populate APIs, with a hierarchic key and an optional copybook so the body is the decoded segment (DFSIOSEG_<SEGMENT>) instead of JDBC columns. Publish from Catalog → IMS-DB → Table APIs.
IMS-DLI
Use IMS-DLI-LOCAL when CoreIQ runs on z/OS, or IMS-DLI-REMOTE when a gateway on z/OS submits the job and CoreIQ calls it over HTTP/S. Browse PSBs, sample reachability, read segment data, apply SSA filters, associate copybooks, and approve healthy PSBs and segments.
On View Segments, use JCL Variables for per-PSB library and DD overrides, and Custom JCL to persist a full DLIBATCH skeleton when the administrator allows user template edits.
See the child pages for PSB sampling, reading segments, JCL variables, Custom JCL, and IMS-DB table APIs.
Read IMS data through IMS-DB table APIs and queries, or native IMS DL/I (local or remote).