Connection to DBCTL

Figure 1 shows an example of the CICS® trace entries produced when CICS connects to DBCTL.

Figure 1. CICS trace entries produced during connection to DBCTL 1 of 2

1                                                      .
                                                       .
2     00028 1 AP 00E1 EIP   ENTRY LINK                                                  0004,07301464 ....,08000E02 ....
      00028 1 PG 1101 PGLE  ENTRY LINK_EXEC             DFHDBCON,07301088 , 00000014
      00028 1 DD 0301 DDLO  ENTRY LOCATE                06D08F80,07301698,PPT,DFHDBCON
      00028 1 DD 0302 DDLO  EXIT  LOCATE/OK             D7D7E3C5 , 06D89858
      00028 1 LD 0001 LDLD  ENTRY ACQUIRE_PROGRAM       06D8BF50
                                                       .
                                                       .
3     00028 1 XM 1101 XMAT  ENTRY ATTACH                CDBO,07302E38 , 00000004,0,NONE,C,NO,YES,NO,0
      00028 1 XM 0401 XMLD  ENTRY LOCATE_AND_LOCK_TRANDEF CDBO
      00028 1 DD 0301 DDLO  ENTRY LOCATE                06D00040,07303314,TXD,CDBO
      00028 1 DD 0302 DDLO  EXIT  LOCATE/OK             06D86B78 , D7000000
                                                       .
                                                       .
4     00028 1 LD 0001 LDLD  ENTRY ACQUIRE_PROGRAM       DFHDBSPX,YES
      00028 1 LD 0002 LDLD  EXIT  ACQUIRE_PROGRAM/OK    870A0020,070A0000
                                                       .
                                                       .
5     00028 1 AP 00E1 EIP   ENTRY ENABLE                                                0004,07302AD4 ...M,08002202 ....
                                                       .
6    1CICS/ESA - AUXILIARY TRACE FROM 07/20/95 - APPLID CICSKPG1 - TIME OF FIRST ENTRY ON THIS PAGE 11:26:58.7144860002
                                                       .
7     00028 1 AP 2522 ERM   EVENT PASSING-CONTROL-TO-TRUE(DBCTL   )
      00028 1 AP 0310 DBAT  ENTRY APPLICATION           REQUEST
8     00028 1 AP 0314 DBAT  EVENT DRA-ROUTER-LOAD       , LOAD-RESPONSE-CODE (00000000)
9     00028 1 AP 0315 DBAT  EVENT ABOUT-TO-INVOKE-DRA   FOR INTERFACE REQUEST , 0100
10    00028 1 AP 0316 DBAT  EVENT RECEIVES-CONTROL-FROM-DRA FOR INTERFACE REQUEST , 00000000
      00028 1 AP 0313 DBAT  EXIT  DBAT-RESPONSE-CODE    (00000000)
11    00028 1 AP 2523 ERM   EVENT REGAINING-CONTROL-FROM-TRUE(DBCTL   )
      00028 1 AP 2521 ERM   EXIT  APPLICATION-CALL-TO-TRUE(DBCTL   )
12    00028 1 ME 0301 MEME  ENTRY SEND_MESSAGE          1FB4,073D642C , 00000004,073D5060 , 00000002,DB
      00028 1 ME 0501 MEIN  ENTRY INQUIRE_MESSAGE_DATA  86BB5AE0,DFHMET1E,1FB4,073039CD , 00000000 , 0000001C,07303967 , 00000000
      00028 1 KE 0101 KETI  ENTRY INQ_LOCAL_DATETIME_DECIMAL
      00028 1 KE 0102 KETI  EXIT  INQ_LOCAL_DATETIME_DECIMAL/OK 07201995,095757,097993,MMDDYYYY
      00028 1 KE 0401 KEGD  ENTRY INQUIRE_KERNEL
      00028 1 KE 0402 KEGD  EXIT  INQUIRE_KERNEL/OK     CICSKPG1,CIA1
      00028 1 ME 0502 MEIN  EXIT  INQUIRE_MESSAGE_DATA/OK 06BB5D7C,06BC5E07,06BC5E1D,06BC5E7C,,I,095757,20071995,M,CIA1,CICSKPG1
      00028 1 ME 0312 MEME  EVENT ISSUE-MVS-GETMAIN
      00028 1 ME 0313 MEME  EVENT MVS-GETMAIN-COMPLETE
13    00028 1 DU 0500 DUDT  ENTRY INQUIRE_SYSTEM_DUMPCODE DB8116
      00028 1 DU 0600 DUTM  ENTRY INQUIRE_SYSTEM_DUMPCODE DB8116
      00028 1 DU 0601 DUTM  EXIT  INQUIRE_SYSTEM_DUMPCODE/EXCEPTION DUMPCODE_NOT_FOUND,0,0,,,,
      00028 1 DU 0501 DUDT  EXIT  INQUIRE_SYSTEM_DUMPCODE/EXCEPTION DUMPCODE_NOT_FOUND,0,0,,,,
      00028 1 ME 0401 MEBU  ENTRY BUILD_MESSAGE         06BC5E07,06BB5D7C,20071995,M,095757,CIA1,CICSKPG1,0730369D , 00000009,073
      00028 1 ME 0402 MEBU  EXIT  BUILD_MESSAGE/OK      0
      00028 1 ME FF35 MEFO  ENTRY -FUNCTION(FORMAT_MESSAGE) 0698B390 , 0000006F,1,78,073039EB , 00000001,YES
      00028 1 ME FF36 MEFO  EXIT  -FUNCTION(FORMAT_MESSAGE) OK
14    00028 1 AP F600 TDA   ENTRY WRITE_TRANSIENT_DATA  CDBC,073039FB , 00000001,NO
                                                       .
                                                       .
15    00028 1 DU 0500 DUDT  ENTRY INQUIRE_SYSTEM_DUMPCODE DB8210
                                                       .
                                                       .
16    00028 1 DU 0500 DUDT  ENTRY INQUIRE_SYSTEM_DUMPCODE DB8292
                                                       .
17                                                     .
      00038 1 DS 0005 DSSR  EXIT  WAIT_MVS/OK
18    00038 1 AP 0306 DBCT  EVENT POSTED                FOR CONNECTION COMPLETE
19    00038 1 ME 0301 MEME  ENTRY SEND_MESSAGE          1FA5,0698B240 , 00000004,073D5060 , 00000002,DB
                                                       .
                                                       .
      00038 1 DU 0500 DUDT  ENTRY INQUIRE_SYSTEM_DUMPCODE DB8101
                                                       .
                                                       .
20    00038 1 GC 2010 CCCC  ENTRY WRITE                 00108194 , 00000008,DBCTL,STATUS
                                                       .
                                                       .
      00038 1 GC 2050 CCCC  EXIT  WRITE/OK
21    00038 1 PG 0A01 PGLU  ENTRY LINK_URM              DFHDBUEX,001081F0 , 0000000B,NO
      00038 1 DD 0301 DDLO  ENTRY LOCATE                06D08F80,00108220,PPT,DFHDBUEX
      00038 1 DD 0302 DDLO  EXIT  LOCATE/OK             D7D7E3C5 , 06D89A50
                                                       .
                                                       .
22    00038 1 AP 0064 USER  EVENT APPLICATION-PROGRAM-ENTRY CONNECT DBCTL HAS JUST BEEN CONNECTED
                                                       .
                                                       .
      00038 1 AP 1941 APLI  EXIT  START_PROGRAM/OK      ....,DFHDBUEX
      00038 1 LD 0001 LDLD  ENTRY RELEASE_PROGRAM       0732B450,86D5B028
      00038 1 LD 0002 LDLD  EXIT  RELEASE_PROGRAM/OK    06D5B000,3A8,ECDSA
      00038 1 PG 0A02 PGLU  EXIT  LINK_URM/OK
      00038 1 AP 00E1 EIP   ENTRY RESYNC                                                0004,001087C4 ..gD,08001604 ....

Figure 2. CICS trace entries produced during connection to DBCTL 2 of 2

22    00038 1 AP 0064 USER  EVENT APPLICATION-PROGRAM-ENTRY CONNECT DBCTL HAS JUST BEEN CONNECTED
                                                       .
                                                       .
      00038 1 AP 1941 APLI  EXIT  START_PROGRAM/OK      ....,DFHDBUEX
      00038 1 LD 0001 LDLD  ENTRY RELEASE_PROGRAM       0732B450,86D5B028
      00038 1 LD 0002 LDLD  EXIT  RELEASE_PROGRAM/OK    06D5B000,3A8,ECDSA
      00038 1 PG 0A02 PGLU  EXIT  LINK_URM/OK
      00038 1 AP 00E1 EIP   ENTRY RESYNC                                                0004,001087C4 ..gD,08001604 ....
                                                       .
                                                       .
23    00038 1 AP E161 EXEC  EXIT  RESYNC                'DBCTL   ' AT X'0713F062','JB1A    ' AT X'8698B270',AT X'00000000',0 AT X
      00038 1 AP E111 EISR  EXIT  TRACE_EXIT/OK
      00038 1 AP 00E1 EIP   EXIT  RESYNC                OK                              00F4,00000000 ....,00001604 ....
      00038 1 AP 00E1 EIP   ENTRY SYNCPOINT                                             0004,001087C4 ..gD,08001602 ....
                                                       .
                                                       .
      00038 1 AP E161 EXEC  EXIT  SYNCPOINT             0,0,ASM,09490000
                                                       .
                                                       .
24    00028 1 ME 0301 MEME  ENTRY RETRIEVE_MESSAGE      2065,000550A7 , 00000000 , 00000033,E,DB
      00028 1 ME 0501 MEIN  ENTRY INQUIRE_MESSAGE_DATA  86BB5AE0,DFHMET1E,2065,07301F95 , 00000000 , 0000001C,07301F2F , 00000000
                                                       .
                                                       .
      00028 1 ME 0502 MEIN  EXIT  INQUIRE_MESSAGE_DATA/OK 06BB5D7C,06BC7416,06BC742C,06BC744D,I,,095759,20071995,M,CIA1,CICSKPG1
      00028 1 DU 0500 DUDT  ENTRY INQUIRE_SYSTEM_DUMPCODE DB8293

Note:

Phase 1 of connection begins.
Locating DFHDBCON and loading if not already loaded. (In this example, CICS and DBCTL have already been connected during this CICS session, so DFHDBCON has already been loaded.)
The control transaction, CDBO, is attached. CDBO enables the DRA to pass information from itself and DBCTL independently of CICS. It is invoked whenever the DRA needs to determine whether to continue processing, which is when:
- The DRA has successfully connected to DBCTL
- DBCTL has been terminated normally using /CHECKPOINT FREEZE or /CHECKPOINT PURGE
- Connection to DBCTL has failed
- A CICS request to connect to DBCTL has been canceled
- The DRA fails
- DBCTL fails
Loading programs needed: DFHDBSPX (shown in example), plus DFHDBCX, DFHDBMOX, DFHDBREX, DFHDBSTX, DFHDBSSX, DFHDBTOX, and DFHDBAT.
DFHDBCON enables DFHDBAT.
A timestamp is included in the header line of every page of CICS abbreviated auxiliary trace output to help you match trace entries with external events.
DFHERM invokes DFHDBAT for connection request.
DRA router module DFSPRRC0 loaded.
DRA is invoked for interface request. The type of interface request is indicated by request type from the PAPL: 0100 is a CONNECT request. (See PAPL request and return codes.)
DBCTL return code (00000000). See Return codes in DBCTL.
Control is passed back to DFHERM.
Phase 1 of connection has ended at this point. Message DFHDB8116 is issued confirming that connection is proceeding. The message includes the DBCTL identifier and the DRA suffix used.
When a message has been issued, the CICS dump domain checks to see if the user has requested any action for that message (using the CEMT SET SYDUMPCODE, or the EXEC CICS SET SYSDUMPCODE commands, (In this case, no dump has been requested, as indicated by DUMPCODE_NOT_FOUND.) However, when you are using abbreviated trace, entries such as INQUIRE_SYSTEM_DUMPCODE DB8116 (in which the system dump code is the message number without the characters DFH) are useful in indicating which messages have been issued. (Complete message numbers are included in full trace.)
Message DFHDB8116 is sent to transient data destination CDBC.
Message DFHDB8210 is issued confirming that connection to DBCTL is proceeding.
Message DFHDB8292 is issued indicating that CICS is in phase 2 of connecting to DBCTL.
At this point, DBCTL exits are loaded, which causes I/O activity. The task is suspended, and the control transaction, CDBO, starts. This is indicated by the task number changing (from 00031 to 00032). Control transaction enters a series of waits. CDBO invokes the CICS-DBCTL interface control program (DFHDBCT).
DBCTL notifies CICS that CICS-DBCTL connection is complete.
Message DFHDB8101 is issued.
A record is written to the global catalog, indicating which DBCTL should be reconnected to if there is a CICS failure. (See Program list table (PLT) and Connecting DBCTL to CICS automatically.)
DFHDBUEX, the CICS-supplied user replaceable program for use with DBCTL, is linked. Trace entries following invocation of DFHDBUEX depend on what you have coded in your own version. (See DFHDBUEX.)
In this example, the user has coded DFHDBUEX to issue a trace entry stating that DBCTL has just been connected.
CICS issues an EXEC CICS RESYNC command to resynchronize any outstanding DBCTL indoubt UOWs. (See Recovery and restart operations for DBCTL.)
Control transaction waits have ended: task number changes back again (from 00032 to 00031). Message DFHDB8293 is issued confirming that DBCTL is connected and ready.