Abbreviated-format CICS trace entries contain much of the information present in the corresponding extended-format trace entries, and they are often sufficient for debugging purposes. There is a one-to-one correspondence between the trace entry numbers for the abbreviated and extended trace entries, so you can easily identify the trace entry pairs.
Abbreviated trace entries show the CICS TCB-ID of the TCB instead of an MVS TCB address.
Figure 28 gives an example of the abbreviated format for an old-style trace entry.
00021 QR AP 00E1 EIP ENTRY INQUIRE-TRACEFLAG 0004,00223810 ....,00007812 .... =000005=
In this example:
Abbreviated old-style trace entries are easy to interpret, as you can readily identify the REQ, FIELD A and FIELD B fields. Note that some such trace entries also include a RESOURCE field.
For ZCP trace entries, FIELD B (which contains the TCTTE address) is printed twice on each line. This allows both sides of the output to be scanned for the terminal entries on an 80-column screen without having to scroll left and right.
Figure 29 gives an example of the abbreviated format for a new-style trace entry.
00021 QR LD 0002 LDLD EXIT ACQUIRE_PROGRAM/OK 03B8A370 , 00000001,848659C0,048659A0,410,200,REUSABLE =000023=
In this example:
Abbreviated-format new-style trace entries are less readily interpreted, because the parameters in the interpretation string are not identified by name. If you are not familiar with the parameters included in the trace entry, you need to look at the corresponding extended-format (or short-format) trace entry to find out what they are. Figure 30 shows the corresponding extended-format trace entry.
LD 0002 LDLD EXIT - FUNCTION(ACQUIRE_PROGRAM) RESPONSE(OK) NEW_PROGRAM_TOKEN(03B8A370 , 00000001) ENTRY_POINT(848659C0) LOAD_POINT
(048659A0) PROGRAM_LENGTH(410) FETCH_TIME(200) PROGRAM_ATTRIBUTE(REUSABLE)
TASK-00021 KE_NUM-0007 TCB-QR /009FF3C0 RET-847B26A2 TIME-10:45:49.6888118129 INTERVAL-00.0000235625 =000023=
1-0000 00880000 0000001C 00000000 00000000 BBA02800 00000000 01000100 C4C6C8C3 *.h..........................DFHC*
0020 D9D84040 FD052000 00062060 03B8A370 00000001 848659C0 048659A0 A4F78696 *RQ .......-..t.....df...f..u7fo*
0040 00000410 C3D9E2D8 00000000 C3C9C3E2 E4E2C5D9 01010002 1C000000 00000000 *....CRSQ....CICSUSER............*
0060 00000000 00000200 C302D840 40000500 01000000 00000000 00000000 00000000 *........C.Q ...................*
0080 00000000 00000000 *........ *
LD 0002 shows that this trace entry was made from trace point X'0002' in the loader domain.
The interpretation string provides this information:
The standard information string gives you this information:
The data displayed below the standard information was taken from only one data area. If you look in Lock Manager Domain trace points for details of trace point ID LD 0002, you will see that the data area is the LDLD parameter list.
The following example denotes the tracing of different TCBs. Notice
in particular that the OTE TCB IDs have a sequential number associated with
them to indicate the TCB that is in use.
00255 QR SM 0D01 SMMF ENTRY FREEMAIN EIIC TEM,1D710958,TEMPSTG =001561=
00256 L9016 SM 0301 SMGF ENTRY GETMAIN CAD0,YES,LE_RUWA,TASK31 =001562=
00255 QR SM 0D02 SMMF EXIT FREEMAIN/OK USER storage at 1D710958 =001563=
00256 L9016 LM 0003 LMLM ENTRY LOCK 1AF55C48,EXCLUSIVE =001564=
00256 L9016 LM 0004 LMLM EXIT LOCK/OK =001565=
00255 L9015 AP 00E1 EIP EXIT RETRIEVE OK 00F4,00000000 ....,0000100A .... =001566=