Collecting data about DBCTL-related problems

DBCTL-related problems can originate from either the CCTL region or one of the IMS regions (CTL, DL/I, DBRC, or IRLM), so it is important to obtain dumps that relate to all these regions.

1. Issue the following IMS commands (because they include region ID numbers and recovery tokens in their various display output):

   /DISPLAY ACTIVE

   /DISPLAY CCTL

   The information that is returned by these commands greatly increases the accuracy and speed that is required to diagnose the problem. The DISPLAY ACTIVE command provides the reasons for waits and region numbers. The DISPLAY CCTL command provides recovery tokens and region numbers. Save the IMS console output.
2. Set the AP portion of the CICS® trace to level 1-2. Save this output.
3. Set the FILE CONTROL portion of the CICS trace to level 1-2. Save this output.
4. Obtain the necessary z/OS® SVC DUMP of the IMS regions by issuing this series of commands:

   DUMP COMM=(dump title)
   R id JOBNAME=(j1,j2,j3,j4,j5,j6),
   SDATA=(CSA,PSA,RGN,SQA,SUM,TRT),END

   In the previous example,

   j1

   is the IMS CTL or DBCTL region job name

   j2

   is the IMS DL/I region job name

   j3

   is the suspicious IMS dependent region job name, if any

   j4

   is the suspicious CCTL (CICS) region name, if any

   j5

   is the IRLM region job name (if IRLM DB locking is used)

   j6

   is the DBRC region job name

5. Save the IMS online log data set that was active during the failure.