Troubleshooting data for IMS problems

CICS® MustGather for IMS problems

IMS problems might occur because a CICS task waits for the CICS IMS task to complete its work in IMS or because a CICS task waits for an open thread TCB to become available in CICS.

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

Required data:

If possible, enter the following IMS command from the console, SDSF, or by using the CICS CDBM transaction:
```
/DISPLAY ACTIVE
```
The MVS™ system dump of both CICS and IMS that is taken when the IMS wait occurs. For more information, see Using dumps for CICS problem determination on z/OS®. Enter this MVS command followed by the reply to capture the dump:
```
DUMP COMM=(dumpname)
R yy,
JOBNAME=
(*MAIN*,cicsjob,XCFAS,ssnmIRLM,ssnmCTRL,ssnmDBRC,ssnmDLI),
SDATA=
(RGN,CSA,SQA,LPA,LSQA,SWA,PSA,ALLNUC,XESDATA,TRT,GRSQ,SUM)
```
where:

dumpname

Contains both the CICS job name and the IMS subsystem.

yy

Specifies the number of the message.

cicsjob

Specifies the CICS region.

ssnm

Specifies the subsystem name of the IMS members.
The MVS system trace that is included in the MVS system dump when MVS internal system trace is on. You can enter MVS TRACE command TRACE ST,128,BR=OFF and TRACE MT,256K to ensure that the system trace is large enough. For more information, see Using trace 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. Turn on level 1-2 tracing for the RI component. When possible, turn on level 1 tracing for all other CICS components. For more information, see Using trace for CICS problem determination on z/OS.

Optional data:

If possible, enter the following MVS Display commands:
```
D A,ALL (or D A,ssnm* or D A,IRL*)
D GRS,CONTENTION
D OPDATA
```
For more information, see Display command in z/OS MVS System Commands.
The CICS message log.
The CICS auxiliary trace or the GTF Trace up until the time when the problem occurs. This might be helpful when you want to identify the cause of the problem, and it is necessary to keep a record of events that lead to the problem over a long period of time.