Troubleshooting data for CICS-MQ adapter and CICS-MQ bridge problems

CICS MustGather for CICS-MQ adapter and CICS-MQ bridge problems

Gather the following diagnostic information before contacting the CICS support team to troubleshoot your CICS-MQ adapter and CICS-MQ bridge problems.

Required data:
  1. The CICS message log and the MVS™ system log (SYSLOG) that contain the messages leading up to the problem.
  2. The MVS system dump that is taken at the point of failure. If you receive an abend and system dumping is permitted for the dump code, a system dump is taken when the error is detected. Otherwise, you can request a dump by following the instructions in the first step under the MVS system dump section in Using dumps for CICS problem determination on z/OS®.
  3. The CICS internal trace that is included in the MVS system dump when tracing is active. For more information, see Using trace for CICS problem determination on z/OS. Ensure that the internal trace table size is big enough to contain sufficient data for diagnosis; for example, you can use a table size of 20480K. Also turn on level 1 tracing for all CICS components if possible.

    Non-exception trace entries for the CICS-MQ adapter are controlled by Resource Manager Interface (RI) and Resource Manager Adapter (RA) level 1 and level 2 tracing. Standard trace is often sufficient, but level 1-2 tracing for the RI and RA components might expedite problem resolution. Bridge facility (BR) standard trace is often sufficient for a CICS-MQ bridge problem, but level 1-2 tracing for the BR component might expedite problem resolution.

Optional data:
  1. The IBM® MQ for z/OS MSTR job log that contains the messages leading up to the problem. The job log is named xxxxMSTR where xxxx is the IBM MQ subsystem identifier (ssid).
  2. Locrec report from the SYS1.LOGREC data set. For more information, see Directions to get Logrec report.
  3. If you need a larger trace, consider using the CICS auxiliary trace or the GTF Trace with the MVS system dump. Use the same level of tracing as documented for CICS internal trace. For more information, see Using trace for CICS problem determination on z/OS.