Troubleshooting data for multiregion operation (MRO) problems

CICS® MustGather for multiregion operation (MRO) problems

Gather the following diagnostic information before contacting the CICS support team to troubleshoot your MRO problems.

Required data:
  1. The CICS message log of both regions in the MRO conversation.
  2. The MVS™ system dump that is taken at the point of failure. Setting system or transaction dump codes by using CEMT is preferred. Ensure that appropriate dump codes are set in both CICS regions within the conversation.For more information, see Using dumps for CICS problem determination on z/OS®.
    Note: Messages or abends might be different on each side of the conversation.
  3. The CICS internal trace of CICS regions that participate in the conversation. 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 standard level 1 tracing for all components and level 1-2 for the IS component. Use the CETR transaction to turn on internal trace, to set internal trace size, and to set component trace levels. For more information, see Using trace for CICS problem determination on z/OS.
Optional data:
  1. If you can re-create the problem, the CICS auxiliary trace might be useful. Ensure that you run the trace on all the CICS regions that are involved in the MRO problem. For more information, see Using trace for CICS problem determination on z/OS.
  2. If you want to see all of the trace entries in one file, you can use the GTF Trace. The GTF Trace is useful in an XCF environment, when the CICS regions are on different MVS regions. You can write the trace to a GTF trace data set on each MVS, and then merge the files to see the flow of trace in the connected regions. If the CICS regions are in a single MVS, you can write all the trace to a single GTF trace data set. For more information, see Using trace for CICS problem determination on z/OS.
  3. The CICS transaction dump that is taken at the point of failure. For more information, see Using dumps for CICS problem determination on z/OS.