Populate from IMS

On IMS → Browse, click Populate from IMS to list transactions through Operations Manager (QUERY TRAN), match COBOL source members, read request and reply layouts from each program’s DL/I calls, and add selected transactions to the IMS catalog.

Prerequisites

On the same host, an administrator must configure:

• An IMS (IMS Connect) endpoint with dataStoreName so Browse can route the Operations Manager query and Test Transaction / published APIs can execute
• An RSE endpoint — listing transactions submits a CSLUSPOC job; without RSE, Populate from IMS stays disabled
• An RSE or JZOS endpoint for COBOL source and copybook PDS access
• An IMS-type catalog assigned to the IMS endpoint

Without IMS + RSE, Populate from IMS stays disabled. One-off Test Transaction still works when the IMS endpoint is present.

Steps

1. Open IMS → Browse and click Populate from IMS.
2. Enter the Transaction filter (required) — Operations Manager QUERY TRAN NAME= mask; use * as a wildcard (for example PAY* or *ACTIM8). An unfiltered query would list every transaction on the IMS.
3. Enter the Source PDS. Optionally set a Copybook PDS when message areas or the I/O PCB live in COPY members.
4. Enter IMSplex and IMS RESLIB (required for Run) — the plex that answers QUERY TRAN, and the STEPLIB dataset that holds CSLUSPOC. These are remembered per host; they are not connection settings.
5. If the host has both RSE and JZOS, choose the Source endpoint.
6. Optionally enable Exclude MFS screen transactions, enter an MFS library, and click Scan. Formats, messages, and transaction codes that drive 3270 screens are marked Screen and are not offered.
7. Click Run. Candidates appear with status chips:
   • Matched — source found and a message layout read from DL/I calls; selectable
   • Void — the transaction carries no data; still addable as a bare call
   • No IO — source found but no message layout could be read; not addable
   • Screen — an MFS format covers this transaction (only filled when a library has been scanned)
   • No source — defined on the host, but no matching source member
   • Associated — already in this catalog
8. Filter the list, use Select all / Select none, then click Add Selected. Each selected transaction is saved or rejected on its own — a single bad row does not fail the batch.

Added entries appear in IMS → Browse and on the Catalog page under the host’s IMS tab. Publish them to expose POST /api/v1/{catalogId}/{endpointName}/{targetName} (the transaction code is the path target).