When examining traces entries produced by CICS® and DBCTL, you need to relate them according to whether they are produced at the same time in CICS and in DBCTL, or at different times. You also need to know how to find the relevant parts of each trace and use them to correlate what is happening in CICS and in DBCTL.
This section covers:
Use the CICS-supplied transaction CETR to trace DBCTL activity. CETR traces DL/I requests until they leave DFHDBAT. See CICS Supplied Transactions for information on using CETR.
The sections that follow give examples of CICS trace entries produced at the following points:
These trace examples were produced using abbreviated auxiliary trace with file control level 1 trace points selected. You will probably find this amount of information sufficient. If it is not, selecting file control level 2 will give you more details on, for example, entry to and exit from DFHDBAT and DFHERM.
See CICS Problem Determination Guide for details of the general format of CICS trace entries, how to select trace options for component and task tracing, whether to use "standard" or "special" tracing, and how to start and stop tracing selectively. Trace point IDs are listed in CICS Diagnosis Reference. See the CICS Operations and Utilities Guide for help on formatting and printing trace entries, including a sample job you can use to do so.
The numbers in the margin to the left of the example traces point to things that you may find useful in correlating CICS and DBCTL activity, but please note that these additional numbers are not part of the trace output. Also note that we have omitted some trace entries for brevity. This is indicated by the following symbol:
.
.
Figure 39 shows an example of the CICS trace entries produced when CICS connects to DBCTL.
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 ....
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
Figure 41 shows some examples of CICS trace entries produced at disconnection from DBCTL.
1 1CICS/ESA - AUXILIARY TRACE FROM 07/20/95 - APPLID CICSKPG1 - TIME OF FIRST ENTRY ON THIS PAGE 11:26:58.7144860002
.
2 .
00047 1 AP 00E1 EIP ENTRY START 0004,07301464 ....,08001008 ....
3 00047 1 XM 0401 XMLD ENTRY LOCATE_AND_LOCK_TRANDEF CDBT
00047 1 DD 0301 DDLO ENTRY LOCATE 06D00040,07301820,TXD,CDBT
00047 1 DD 0302 DDLO EXIT LOCATE/OK 06D86C10 , D7000000
.
.
4 00047 1 DU 0500 DUDT ENTRY INQUIRE_SYSTEM_DUMPCODE DB8211
.
.
5 00047 1 DU 0500 DUDT ENTRY INQUIRE_SYSTEM_DUMPCODE DB8294
.
.
6 00048 1 PG 0901 PGPG ENTRY INITIAL_LINK DFHDBDSC
.
.
7 00048 1 AP 00E1 EIP ENTRY ADDRESS 0004,0005B010 ....,08000202 ....
.
.
8 00048 1 PG 0A01 PGLU ENTRY LINK_URM DFHDBUEX,0005B0C4 , 0000000B,NO
00048 1 DD 0301 DDLO ENTRY LOCATE 06D08F80,0005B3A4,PPT,DFHDBUEX
00048 1 DD 0302 DDLO EXIT LOCATE/OK D7D7E3C5 , 06D89A50
00048 1 LD 0001 LDLD ENTRY ACQUIRE_PROGRAM 0732B450
00048 1 LD 0002 LDLD EXIT ACQUIRE_PROGRAM/OK 86D5B028,06D5B000,3A8,0,REUSABLE,ECDSA,OLD_COPY
9 00048 1 AP 1940 APLI ENTRY START_PROGRAM DFHDBUEX,NOCEDF,FULLAPI,URM,NO,07309828,0005B0C4 , 0000000B,2
.
.
00048 1 AP 0065 USER EVENT APPLICATION-PROGRAM-ENTRY DISCONN DBCTL HAS JUST BEEN DISCONNECTED
.
.
10 00048 1 LD 0001 LDLD ENTRY RELEASE_PROGRAM 0732B450,86D5B028
00048 1 LD 0002 LDLD EXIT RELEASE_PROGRAM/OK 06D5B000,3A8,ECDSA
00048 1 PG 0A02 PGLU EXIT LINK_URM/OK
00048 1 AP 2520 ERM ENTRY APPLICATION-CALL-TO-TRUE(DBCTL )
.
.
00048 1 AP 2522 ERM EVENT PASSING-CONTROL-TO-TRUE(DBCTL )
00048 1 AP 0310 DBAT ENTRY APPLICATION REQUEST
11 00048 1 AP 0315 DBAT EVENT ABOUT-TO-INVOKE-DRA FOR INTERFACE REQUEST , 0400
12 00048 1 AP 0304 DBSPX EVENT ABOUT-TO-ISSUE-WAIT FOR DISCONNECTION REQUEST
00048 1 DS 0004 DSSR ENTRY WAIT_MVS DLSUSPND,DBCTL,0005B444,NO,OTHER_PRODUCT
00048 1 DS 0005 DSSR EXIT WAIT_MVS/OK
00048 1 AP 0305 DBSPX EVENT POSTED FOR DISCONNECTION REQUEST
13 00048 1 AP 0316 DBAT EVENT RECEIVES-CONTROL-FROM-DRA FOR INTERFACE REQUEST , 00000000
.
.
14 00048 1 ST 0003 STST ENTRY RECORD_STATISTICS 072F7618 , 00000054,USS
.
.
00048 1 ST 0004 STST EXIT RECORD_STATISTICS/OK
00048 1 AP 0313 DBAT EXIT DBAT-RESPONSE-CODE (00000000)
00048 1 AP 2523 ERM EVENT REGAINING-CONTROL-FROM-TRUE(DBCTL )
00048 1 AP 2521 ERM EXIT APPLICATION-CALL-TO-TRUE(DBCTL )
15 00048 1 GC 2010 CCCC ENTRY WRITE 0005B0BC , 00000008,DBCTL,STATUS
16 .
.
00048 1 DS 0004 DSSR ENTRY WAIT_MVS ASYNRESP,CCVSAMWT,06C8D5C0,NO,IO
00038 1 DS 0005 DSSR EXIT WAIT_MVS/OK
17 00038 1 AP 0306 DBCT *EXC* EVENT POSTED FOR DFHDBCT SHOULD TERMINATE
00038 1 AP 00E1 EIP ENTRY START 0004,001087C4 ..gD,08001008 ....
.
.
00038 1 XM 0401 XMLD ENTRY LOCATE_AND_LOCK_TRANDEF CDBD
00038 1 DD 0301 DDLO ENTRY LOCATE 06D00040,0730C078,TXD,CDBD
00038 1 DD 0302 DDLO EXIT LOCATE/OK 06D86918 , D7000000
.
.
00038 1 AP 00F3 ICP ENTRY INITIATE CDBD 4003,0000000C ....,00000000 ....,CDBD
.
.
18 00049 1 LD 0001 LDLD ENTRY RELEASE_PROGRAM DFHDBSSX,8711A910
00049 1 LD 0002 LDLD EXIT RELEASE_PROGRAM/OK
.
.
00049 1 ME 0502 MEIN EXIT INQUIRE_MESSAGE_DATA/OK 06BB5D7C,06BC56B8,06BC56CE,06BC5710,,I,100011,20071995,M,CIA1,CICSKPG1
19 00049 1 DU 0500 DUDT ENTRY INQUIRE_SYSTEM_DUMPCODE DB8102
If there is DL/I activity at the time of the disconnect, and the disconnect is orderly (not immediate) DFHDBAT links to DFHDBSPX (the CICS-DBCTL suspend exit) to wait for all DL/I activity to complete. In this example, there was no DL/I activity at the time the disconnect was issued.
Figure 42 shows an example of some CICS trace entries produced at PSB schedule time.
.
.
1 1CICS/ESA - AUXILIARY TRACE FROM 07/20/95 - APPLID CICSKPG1 - TIME OF FIRST ENTRY ON THIS PAGE 11:26:58.7144860002
.
.
00039 1 AP 00E1 EIP ENTRY CALLDLI 0004,00182718 ....,00004000 .. .
2,3 00039 1 AP 0328 DLI ENTRY FUNCTION_CODE(PCB ) 000C7526,TDLRA1
.
.
00039 1 AP 0330 DLIDP ENTRY DBCTL
.
.
00039 1 AP 2520 ERM ENTRY APPLICATION-CALL-TO-TRUE(DBCTL )
.
.
00039 1 AP 2522 ERM EVENT PASSING-CONTROL-TO-TRUE(DBCTL )
00039 1 AP 0310 DBAT ENTRY APPLICATION REQUEST
4,5 00039 1 AP 0311 DBAT EVENT ABOUT-TO-INVOKE-DRA FOR THREAD REQUEST , C3C9C3E2D2D7C7F1AB6538123994CA01,0301
6 00039 1 AP 0304 DBSPX EVENT ABOUT-TO-ISSUE-WAIT FOR THREAD REQUEST
00039 1 DS 0004 DSSR ENTRY WAIT_MVS DLSUSPND,DBCTL,0732001C,NO,OTHER_PRODUCT
00039 1 DS 0005 DSSR EXIT WAIT_MVS/OK
00039 1 AP 0305 DBSPX EVENT POSTED FOR THREAD REQUEST
4,7 00039 1 AP 0312 DBAT EVENT RECEIVES-CONTROL-FROM-DRA FOR THREAD REQUEST , C3C9C3E2D2D7C7F1AB6538123994CA01,00000000
00039 1 AP 0313 DBAT EXIT DBAT-RESPONSE-CODE (00000000)
00039 1 AP 2523 ERM EVENT REGAINING-CONTROL-FROM-TRUE(DBCTL )
.
.
00039 1 AP 2521 ERM EXIT APPLICATION-CALL-TO-TRUE(DBCTL )
00039 1 AP 0331 DLIDP EXIT DBCTL
00039 1 AP 0329 DLI EXIT IMS_PCB_FORMAT 0000,0000,PCB
8 00039 1 AP 00E1 EIP EXIT CALLDLI OK 00F4,00000000 ....,00004000 .. .
Figure 43 shows an example of the trace entries produced if PSB scheduling fails.
1 1CICS/ESA - AUXILIARY TRACE FROM 07/20/95 - APPLID CICSKPG1 - TIME OF FIRST ENTRY ON THIS PAGE 11:26:58.7144860002
.
.
00064 1 AP 00E1 EIP ENTRY CALLDLI 0004,00182718 ....,00004000 .. .
2,3 00064 1 AP 0328 DLI ENTRY FUNCTION_CODE(PCB ) 000C8946,TXLRA1
.
.
00064 1 AP 0330 DLIDP ENTRY DBCTL
.
.
00064 1 AP 2520 ERM ENTRY APPLICATION-CALL-TO-TRUE(DBCTL )
.
.
00064 1 AP 2522 ERM EVENT PASSING-CONTROL-TO-TRUE(DBCTL )
00064 1 AP 0310 DBAT ENTRY APPLICATION REQUEST
4,5 00064 1 AP 0311 DBAT EVENT ABOUT-TO-INVOKE-DRA FOR THREAD REQUEST , C3C9C3E2D2D7C7F1AB654BD5E4F07E04,0301
6 00064 1 AP 0304 DBSPX EVENT ABOUT-TO-ISSUE-WAIT FOR THREAD REQUEST
00064 1 DS 0004 DSSR ENTRY WAIT_MVS DLSUSPND,DBCTL,0732001C,NO,OTHER_PRODUCT
00064 1 DS 0005 DSSR EXIT WAIT_MVS/OK
00064 1 AP 0305 DBSPX EVENT POSTED FOR THREAD REQUEST
00064 1 AP 0312 DBAT EVENT RECEIVES-CONTROL-FROM-DRA FOR THREAD REQUEST , C3C9C3E2D2D7C7F1AB654BD5E4F07E04,880001AC
00064 1 AP 0313 DBAT EXIT DBAT-RESPONSE-CODE (00000000)
00064 1 AP 2523 ERM EVENT REGAINING-CONTROL-FROM-TRUE(DBCTL )
00064 1 AP 2521 ERM EXIT APPLICATION-CALL-TO-TRUE(DBCTL )
00064 1 ME 0301 MEME ENTRY SEND_MESSAGE 1FAD,00051230 , 00000004,0011F5D0 , 00000005,0011F5D5 , 00000008,0011F3CC
00064 1 ME 0501 MEIN ENTRY INQUIRE_MESSAGE_DATA 86BB5AE0,DFHMET1E,1FAD,073017ED , 00000000 , 0000001C,07301787 , 00000000
.
.
7 00064 1 DU 0500 DUDT ENTRY INQUIRE_SYSTEM_DUMPCODE DB8109
.
.
00064 1 AP 0331 DLIDP EXIT DBCTL
8 00064 1 AP 0329 DLI EXIT IMS_PCB_FORMAT 0805,0000,PCB
00064 1 AP 00E1 EIP EXIT CALLDLI OK 00F4,00000000 ....,00004000 .. .
Figure 44 shows an example of CICS trace entries produced when a DL/I request is issued. For an example of trace entries produced by DBCTL for processing of a DL/I request, see Trace entries produced by DBCTL.
1 1CICS/ESA - AUXILIARY TRACE FROM 07/20/95 - APPLID CICSKPG1 - TIME OF FIRST ENTRY ON THIS PAGE 11:26:58.7144860002
00040 1 AP 00E1 EIP ENTRY CALLDLI 0004,00183718 ....,00004000 .. .
2,3 00040 1 AP 0328 DLI ENTRY FUNCTION_CODE(GU ) 0001A8AC,DLIDBDR
00040 1 AP 0330 DLIDP ENTRY DBCTL
00040 1 AP 2520 ERM ENTRY APPLICATION-CALL-TO-TRUE(DBCTL )
00040 1 AP 2522 ERM EVENT PASSING-CONTROL-TO-TRUE(DBCTL )
00040 1 AP 0310 DBAT ENTRY APPLICATION REQUEST
4,5 00040 1 AP 0311 DBAT EVENT ABOUT-TO-INVOKE-DRA FOR THREAD REQUEST , C3C9C3E2D2D7C7F1AB653817A31F9000,0303
00040 1 AP 0304 DBSPX EVENT ABOUT-TO-ISSUE-WAIT FOR THREAD REQUEST
00040 1 DS 0004 DSSR ENTRY WAIT_MVS DLSUSPND,DBCTL,0739501C,NO,OTHER_PRODUCT
00041 1 DS 0005 DSSR EXIT WAIT_MVS/OK
00041 1 AP 0305 DBSPX EVENT POSTED FOR THREAD REQUEST
4,6 00041 1 AP 0312 DBAT EVENT RECEIVES-CONTROL-FROM-DRA FOR THREAD REQUEST , C3C9C3E2D2D7C7F1AB653817A6C96600,00000000
00041 1 AP 0313 DBAT EXIT DBAT-RESPONSE-CODE (00000000)
00041 1 AP 2523 ERM EVENT REGAINING-CONTROL-FROM-TRUE(DBCTL )
00041 1 RM 0301 RMLN ENTRY SET_LINK 01050000,073D69D4 , 00000000 , 00000008,NECESSARY,
00041 1 RM 0302 RMLN EXIT SET_LINK/OK
00041 1 AP 2521 ERM EXIT APPLICATION-CALL-TO-TRUE(DBCTL )
00041 1 AP 0331 DLIDP EXIT DBCTL
7 00041 1 AP 0329 DLI EXIT IMS_PCB_FORMAT 0000,0000,PCB
00041 1 AP 00E1 EIP EXIT CALLDLI OK 00F4,00000000 ....,0 0004000 .. .
Figure 45 shows example trace entries produced during PREPARE, COMMIT, and TERMINATE request processing. See Two-phase commit for DBCTL for a description of PREPARE and COMMIT request processing.
.
.
1 1CICS/ESA - AUXILIARY TRACE FROM 07/20/95 - APPLID CICSKPG1 - TIME OF FIRST ENTRY ON THIS PAGE 09:59:09.1299476250
2 00039 1 AP 2520 ERM ENTRY SYNCPOINT-MANAGER-CALL-TO-TRUE(DBCTL )
00039 1 AP 2522 ERM EVENT PASSING-CONTROL-TO-TRUE(DBCTL )
00039 1 AP 0310 DBAT ENTRY SYNCPOINT-MANAGER REQUEST
3,4 00039 1 AP 0311 DBAT EVENT ABOUT-TO-INVOKE-DRA FOR THREAD REQUEST , C3C9C3E2D2D7C7F1AB6538123994CA01,0304
00039 1 AP 0304 DBSPX EVENT ABOUT-TO-ISSUE-WAIT FOR THREAD REQUEST
00039 1 DS 0004 DSSR ENTRY WAIT_MVS DLSUSPND,DBCTL,0732001C,NO,OTHER_PRODUCT
00039 1 DS 0005 DSSR EXIT WAIT_MVS/OK
00039 1 AP 0305 DBSPX EVENT POSTED FOR THREAD REQUEST
3,5 00039 1 AP 0312 DBAT EVENT RECEIVES-CONTROL-FROM-DRA FOR THREAD REQUEST , C3C9C3E2D2D7C7F1AB6538123994CA01,00000000
00039 1 AP 0313 DBAT EXIT DBAT-RESPONSE-CODE (00000004)
00039 1 AP 2523 ERM EVENT REGAINING-CONTROL-FROM-TRUE(DBCTL )
00039 1 AP 2521 ERM EXIT SYNCPOINT-MANAGER-CALL-TO-TRUE(DBCTL )
.
.
00039 1 AP 2520 ERM ENTRY SYNCPOINT-MANAGER-CALL-TO-TRUE(DBCTL )
00039 1 AP 2522 ERM EVENT PASSING-CONTROL-TO-TRUE(DBCTL )
00039 1 AP 0310 DBAT ENTRY SYNCPOINT-MANAGER REQUEST
3,6 00039 1 AP 0311 DBAT EVENT ABOUT-TO-INVOKE-DRA FOR THREAD REQUEST , C3C9C3E2D2D7C7F1AB6538123994CA01,0307
00039 1 AP 0304 DBSPX EVENT ABOUT-TO-ISSUE-WAIT FOR THREAD REQUEST
00039 1 DS 0004 DSSR ENTRY WAIT_MVS DLSUSPND,DBCTL,0732001C,NO,OTHER_PRODUCT
.
.
00039 1 DS 0005 DSSR EXIT WAIT_MVS/OK
00039 1 AP 0305 DBSPX EVENT POSTED FOR THREAD REQUEST
3,5 00039 1 AP 0312 DBAT EVENT RECEIVES-CONTROL-FROM-DRA FOR THREAD REQUEST , C3C9C3E2D2D7C7F1AB6538123994CA01,00000000
00039 1 MN 0201 MNMN ENTRY MONITOR 1,DBCTL,7320090,100
00039 1 MN 0202 MNMN EXIT MONITOR/OK
3,7 00039 1 AP 0311 DBAT EVENT ABOUT-TO-INVOKE-DRA FOR THREAD REQUEST , C3C9C3E2D2D7C7F1AB6538123994CA01,030F
00039 1 AP 0304 DBSPX EVENT ABOUT-TO-ISSUE-WAIT FOR THREAD REQUEST
00039 1 DS 0004 DSSR ENTRY WAIT_MVS DLSUSPND,DBCTL,0732001C,NO,OTHER_PRODUCT
.
.
00039 1 DS 0005 DSSR EXIT WAIT_MVS/OK
00039 1 AP 0305 DBSPX EVENT POSTED FOR THREAD REQUEST
3,5 00039 1 AP 0312 DBAT EVENT RECEIVES-CONTROL-FROM-DRA FOR THREAD REQUEST , C3C9C3E2D2D7C7F1AB6538123994CA01,00000000
00039 1 AP 2523 ERM EVENT REGAINING-CONTROL-FROM-TRUE(DBCTL )
8 00039 1 AP 2521 ERM EXIT SYNCPOINT-MANAGER-CALL-TO-TRUE(DBCTL )
In DBCTL, tracing is started by specifying an option in member DFSVSMxx in the IMS.PROCLIB (where xx is the suffix specified by VSPEC= in the DBCTL startup JCL). See the IMS System Definition Reference manual manual or IMS Installation Volume 2: System Definition and Tailoring for guidance on the DFSVSMxx member. Alternatively, you can start tracing dynamically with the /TRACE command. (See the IMS Operator’s Reference manual for guidance on the /TRACE command and its keywords.)
In DBCTL, you can start PI tracing in the DFSVSMxx member of the IMS.PROCLIB, as explained above. Alternatively, you can start PI tracing in DBCTL by issuing the command:
/TRACE SET ON PI
DBCTL produces an external trace when DL/I requests are issued to be processed by DBCTL. This trace corresponds to the CICS trace for a DL/I request being processed by DBCTL, as shown in Figure 44. (DBCTL does not produce any external traces that correspond with the other CICS trace examples given.)
Figure 46 shows an example of the trace records produced when you use the DL/I trace table. To start the DL/I trace table, DLI=ON must have been specified in the DFSVSMxx member of IMS.PROCLIB. Specifying DLI=ON also enables program isolation and lock trace. For guidance on specifying DLI=ON, see the IMS System Definition Reference manual manual or IMS Installation Volume 2: System Definition and Tailoring. Alternatively, you can start DL/I tracing dynamically using the /TRACE command, as follows:
/TRACE SET ON TABLE DL/I
For a more detailed example, see the IMS Operator’s Reference manual, example 8.
The DBCTL trace entry shown in Figure 46 includes:
You can print and format the above data using the IMS file select and formatting print utility, DFSERA10. You would typically print and format several log types, plus the X'AC' records to enable you to correlate the DBCTL activity with your CICS trace for a DL/I request.
Figure 47 shows an example of JCL and DD statements that you can use to print and format IMS X'67FA' log records. For further examples, see the IMS Utilities Reference: Database manual manual.
//LOGPRINT JOB 1,PGMERID,MSGCLASS=A,MSGLEVEL=(1,1),
// CLASS=A
//ERA10 EXEC PGM=DFSERA10,REGION=4096K
//STEPLIB DD DISP=SHR,DSN=IMS.RESLIB
//SYSPRINT DD SYSOUT=*,DCB=(RECFM=FBA,LRECL=133,BLKSIZE=1330)
//LOGIN DD DISP=SHR,DSN=IMS.SLDS.OLDS00
//SYSIN DD *
CONTROL CNTL DDNAME=LOGIN
OPTION PRINT OFFSET=5,FLDLEN=2,VALUE=67FA,COND=E,EXITR=DFSERA60
END
/*
//
The output should contain the following:
See the IMS Utilities Reference: Database manual manual for examples of formatted DL/I trace tables.