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.
The Db2 keyword can specify
the following values:
0 - no Db2 output
1 - summary information only
2 - control blocks only
3 - summary and control blocks
In a CICS transaction dump, no summary or control blocks appear but the trace table contains the
CICS Db2 trace entries.
A sample showing CICS Db2
summary information from a CICS system dump is shown in Figure 1. The sample
provides information on the global state of the CICS Db2 connection, and a summary of
transactions (under the headings "Tran id", "Task num", "TcaAddr", "TieAddr", "LotAddr", "Rctename",
"RcteAddr", "CsubAddr", "Correlation id", "Uowid", "Subtask running", and "TCB in DB2"). This sample
was output when CICS was connected to DB2® Version 6
using the open transaction environment. Figure 1. Dump example
===DB2: CICS/DB2 - SUMMARY
==DB2: GLOBAL STATE SUMMARY
Db2conn name: RCTJT
Connection status: Connected
In standby mode: No
DB2 id: DE2D
DB2 Group id:
DB2 release: 0610
Operating in OpenAPI mode: Yes
Service task started: Yes
Main subtask started: No - not required
Tcb limit: 12
Currently active tcbs: 2
Message Queue1: CDB2
Message Queue2:
Message Queue3:
Statistics Queue: CDB2
Standbymode: Reconnect
Connecterror: Sqlcode
==DB2: TRANSACTION SUMMARY
Tran Task TcaAddr TieAddr LotAddr Rctename RcteAddr CsubAddr Correlation Uowid Subtask TCB
id num id running in DB2
--------------------------------------------------------------------------------------------------------------
XP05 00050 184AB680 190442F0 19044370 XP05 18DF2D78 18D10330 ENTRXP050002 B60A17A16316E1C7 N/A Yes
XP05 00048 184AC680 19044190 19044210 XP05 18DF2D78 18D10030 ENTRXP050001 B60A1794A7A9E7C4 N/A No