Troubleshooting data for program check or abend problems

CICS® MustGather for program check or abend problems

Gather the following diagnostic information before contacting the CICS support team to troubleshoot your program check or abend problems.

Required data:

The CICS message log that contains the messages leading up to the abend with the abend code and the abend message.
If multiple abends occur within the same time frame (seconds), the first abend is often the cause of subsequent abends. Therefore, ensure that you send the diagnostic information for the initial abend to IBM® Support, unless the information is not available or you are otherwise requested.
The MVS™ system dump that is taken at the point of failure. If system dumping is permitted for the dump code and system dumping is not disabled, a system dump is taken when the error is detected. See number 3 under the MVS system dump section in Using dumps for CICS problem determination on z/OS® if you do not get a dump when the abend occurs.

Optional data:

The CICS transaction dump that is taken at the point of failure. The transaction dump often does not contain enough information to diagnose the problem. Therefore, if you have only one transaction dump and the problem is re-creatable, you can request a system dump by entering one of the following commands:
- ```
CEMT SET TRD(xxxx) SYS MAX(1) ADD
```
  where xxxx is the transaction abend code.
  
  Ensure that MAX is 1 greater than CUR to capture a dump. Check this by entering CEMT INQ TRD(xxxx).
- ```
CEMT SET SYD(xxxxx) SYS MAX(1) ADD
```
  where xxxxx is the CICS message without the DFH.
  
  Enter this command to request a system dump when you receive CICS messages at the time of the error. It is common to suppress dumps for dump code AP0001. Make sure that you do not suppress dumps for AP0001 by entering CEMT INQ SYS(AP0001) and ensuring that SYS is specified.
For more information, see Using dumps for CICS problem determination on z/OS.
The CICS internal trace that is included in the MVS system dump when tracing is active. 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. When possible, turn on level 1 tracing for all CICS components. For more information, see Using trace for CICS problem determination on z/OS.