Troubleshooting data for Db2 problems

CICS® MustGather for Db2 problems

A CICS task might wait for the CICS Db2 task to complete its work in Db2. A CICS task might also wait for an open thread TCB to become available in CICS. See CICS Db2 waits for a more possible cause. You might also have a Db2 problem in CICS TS that is not related to a wait.

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

Required data:

For General Db2 problems, you must collect the following data:

The MVS system dump of both CICS and Db2 that is taken when the CICS Db2 problem 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,ssnmMSTR,ssnmDBM1),
SDATA=
(RGN,CSA,SQA,LPA,LSQA,SWA,PSA,ALLNUC,XESDATA,TRT,GRSQ,SUM)
```
where:

dumpname

Contains both the CICS job name and Db2 subsystem.

yy

Specifies the number of the message.

cicsjob

Specifies the CICS region.

ssnm

Specifies the subsystem name of the Db2 members.
The MVS system trace that is included in the MVS system dump when the MVS internal system trace is on. You can enter MVS TRACE commands 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 RA and RI components. 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.

For Db2 wait problems, in addition to the previous material, collect the following data:

As detailed in Db2 Information APAR II14016 with regard to MVS SYSLOG, to enable reference to the DSNV404I response output that results from entering the following Db2 commands at the point of the wait:
```
-DISPLAY THREAD(*) DETAIL
```
If possible, enter the following commands:
```
-DISPLAY DATABASE(*) USE/LOCKS LIMIT(*)
-DISPLAY UTILITY (*)
```

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

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.