IBM IMS Queue Control Facility for z/OS interface

You can invoke the IBM® IMS™ Queue Control Facility for z/OS® functions through either a user control card input or a TSO/ISPF interface. The functions are Browse, Query, Load/Insert, Queue Overflow Protection, Recover, and Unload.

The following figure describes the IMS Queue Control Facility interface to IMS.

Figure 1. IMS Queue Control Facility interface to IMS

Figure shows the IMS Queue Control Facility interface to IMS and is fully explained in the text that follows.

The functions are processed by function routines within IMS Queue Control Facility, and passed to corresponding function routines in IMS through a BMP application program interface (API). GCMD calls are used to invoke the function, and the messages, query, and status data is exchanged through GCMD, ISRT/PURGE, and GU/GN calls.

The IMS Queue Control Facility function routines interface with the IMS Queue Manager and Common Queue Server (CQS) routines.

By using the standard AIB interface, errors detected are recorded with an AIB return code = 000000F0, a unique AIBREASN code for each error, a TPCBSTAT code of MR, and a 6701-MRQE log record is written to the IMS online log data set (OLDS). The AIBREASN codes are printed in the reports (Browse, Query, Load, Recover, and Unload) and are documented in the DFSMRAEQ macro.

After the error is reported and logged, IMS Queue Control Facility and IMS skip to the next message, function, or terminate the BMP, depending on the error. The IMS Queue Control Facility routines in IMS do not abend. To diagnose the error, the 6701-MRQE log records should be printed and analyzed. The API calls may also be traced by IMS Queue Control Facility (Trace control card), or within IMS by issuing the /TRACE SET ON PROGRAM MRQPSB. The IMS Queue Control Facility trace sends output to the QCFPRINT DD data set. The IMS trace logs type 6701 records to the OLDS.