Troubleshooting DB2
This section discusses problem determination for CICS® DB2®.
These topics contain Diagnosis, Modification or Tuning information.
- Thread TCBs (task control blocks)
In the CICS DB2 environment, each thread into DB2 runs under a thread task control block (TCB). This section provides further technical information about thread TCBs, to assist with problem determination. - Wait types for CICS DB2
The CICS DB2 task-related user exit, DFHD2EX1, issues WAIT_MVS calls for different purposes, these calls are distinguished by their resource name and type values. The resource name and resource type values are visible in the dispatcher section of a CICS system dump and also appear on the CEMT INQUIRE TASK panel as Hty and Hva values respectively. - Messages for CICS DB2
Messages issued by the CICS DB2 attachment facility use the DFHDB prefix which is also used for CICS DBCTL messages. Message numbers are in the range 2000 through 2999 and are reserved for CICS DB2. Thus CICS DB2 attachment messages are of the form DFHDB2xxx. - Trace for CICS DB2
The CICS DB2 attachment facility uses AP domain trace points in the range 3100 to 33FF. - Dump for CICS DB2
Control blocks from the CICS DB2 attachment facility are formatted out in a CICS system dump under the control of the DB2 keyword of the CICS IPCS verbexit. - DB2 thread identification
A thread executing in DB2 on behalf of a CICS transaction is identified by its correlation ID, which is set by the CICS DB2 Attachment Facility. - Transaction abend codes for CICS DB2
The CICS DB2 attachment facility uses multiple abend codes, each of which is unique to a particular error. - Execution Diagnostic Facility (EDF) for CICS DB2
The CICS DB2 task-related user exit, DFHD2EX1, is enabled with the FORMATEDF keyword and is called by CICS to format the screen for SQL API requests when the transaction is being run under EDF. - Handling deadlocks in the CICS DB2 environment
Deadlocks can occur in a CICS DB2 system between two or more transactions or between one transaction and another DB2 user. Deadlocks can involve one or two resources.
dfhtk2n.html |
Last updated: Monday, 5 June 2017