Obtaining diagnostics in addition to SCRAPLOG and 6701-MRQE

When the 6701-MRQE diagnostic records and the SCRAPLOG records do not provide enough diagnostic detail to adequately diagnose a problem, you can obtain additional diagnostic details by issuing the /TRACE SET ON PROGRAM command. /TRACE SET ON pgmname causes the logging of additional 6701-MRQB records when the QCF BMP is processing.

When the 6701-MRQE diagnostic records and the SCRAPLOG records do not provide enough diagnostic detail to adequately diagnose a problem, you can obtain additional diagnostic details by issuing the following command:

/TRACE SET ON PROGRAM pgmname

where pgmname is the name of the appropriate MRQPSB.

6701-MRQB diagnostic records are almost identical to 6701-MRQE records, with the exception of MRQB appearing where MRQE normally does. The pgmname value is the default QCF PSBNAME. This value might have been overridden on the MSGQUEUE MRQPSBN parameter at system definition. To determine if your installation has overridden the name, either consult with your IMS™ system administrator or issue the IMS command /DISPLAY PROGRAM MRQPSB.

If PROGRAM MRQPSB displays as an invalid name, your installation has overridden the default MRQPSB. Consult with your system administrator for the correct name for your installation.

The records that are contained in this program are in addition to the existing program trace records logged by DFSDLA30. Records logged by DFSDLA30 are types 6701-LA3A and 6701-LA3B, which contain the TPCB, I/O AREA (64 bytes), and PST control blocks.

With the program trace set on, for each ISRT call to insert a message (or segment of a message), there is an LA3A, MRQB, and LA3B record. For each PURG call (which completes and enqueues a message) there is one LA3A and LA3B log record. If an error is detected while processing either call, an additional MRQE record is logged. The MRQE records are logged regardless of whether the program trace is on when an error is detected.