CICS system trace entries made to the internal trace table, the auxiliary trace data sets, and the GTF trace data set can all be formatted to give the same type of information.
There are two slightly different extended trace entry formats. One ("old-style") resembles the format used in earlier releases of CICS, and gives FIELD A and FIELD B values. The other ("new-style") uses a completely new format, described below.
Both types of formatted trace entries always show:
Its format is always a two-character domain index, showing which domain the trace point is in, then a space, then a four-digit (two-byte) hexadecimal number identifying the trace point within the domain.
The following are examples of trace point IDs:
AP 00E1 trace point X'00EE' in Application Domain
DS 0005 trace point X'0005' in Dispatcher Domain
TI 0101 trace point X'0101' in Timer Domain
For old-style trace points, these are shown as fixed length (4-byte) FIELD A and FIELD B values in the same line as the interpretation string. Both the hexadecimal data values and any printable EBCDIC characters that they represent are shown.
For new-style trace points, 1-7 variable-length data fields can be given. They are shown immediately below the standard information line. Any printable EBCDIC characters represented by byte values in the data fields are shown on the right of the trace.
Some of the data fields in the new trace entries contain material intended for use by IBM® support personnel and you cannot interpret them directly. However, there is enough information to resolve user errors and for IBM support personnel to resolve most system errors in the interpretation string for the entry. Trace entries from old-style trace points also include a request type field (REQ), which gives the same information as the two-byte request field in the formatted trace entries of CICS/MVS Version 2.
Some old-style trace entries also have a RESOURCE field. When provided, it is usually the name of a resource associated with the request being traced. For example, for program control requests, it is the program name.
Figure 24 shows a trace entry made from an old-style trace point. Its trace point ID is AP 00E1, corresponding to trace ID X'E1' of CICS/MVS Version 2. If you are migrating from CICS/MVS Version 2, you can probably see the resemblance between this type of format and the one it replaces.
AP 00E1 EIP EXIT SYNCPOINT OK REQ(00F4) FIELD-A(00000000 ....) FIELD-B(00001602 ....)
TASK-00163 KE_NUM-0007 TCB-QR /009F3338 RET-8413F470 TIME-16:32:01.1291125625 INTERVAL-00.0000216875 =000725=
The following is an explanation of the old-style trace entry:
Note that although all old-style trace points are in AP domain, not all AP domain trace points are old-style. Some are new trace points, and they have a similar format to that shown in Figure 25. In general, old-style trace points have values less than or equal to X'00FF' and new AP-domain trace points have values greater than or equal to X'0200'
FIELD-A bytes 0-3 would contain the secondary response, EIBRESP2. FIELD-B bytes 0-1 would contain the condition number, EIBRESP. In this example, both are zero, indicating that no error response has been returned. FIELD-B bytes 2-3 contain the command code, EIBFN. In this example, this is X'1602', showing that the EXEC CICS command was SYNCPOINT.
Look now at Figure 25, which shows a new-style trace entry.
SM 0C01 SMMG ENTRY - FUNCTION(GETMAIN) GET_LENGTH(1A4A) SUSPEND(YES) INITIAL_IMAGE(00) STORAGE_CLASS(TASK)
TASK-00163 KE_NUM-0007 TCB-QR /009F3338 RET-800411F2 TIME-16:31:52.5916976250 INTERVAL-00.0000666250 =000112=
1-0000 00480000 00000011 00000000 00000000 B6700000 00000000 02000100 C4C6C8C3 *............................DFHC*
0020 C5E3D9C4 03BD5BB0 00001A4A 03BD5B01 00000001 01000698 04755D70 40400008 *ETRD..$.... ..$........Q..). ..*
0040 00000FE8 C3C5E3D9 *...YCETR *
The following is an explanation of the new-style trace entry:
Storage Manager domain trace points contains details of trace point ID SM 0C01. The data area is the SMMG parameter list.
Relevant information is formatted from the data area and appears in the trace entry interpretation string.
Note that information about some data areas is intended for use by IBM support personnel, and this means that details of their format and contents might not be available to you. If you reach a point at which you are certain that you cannot continue the problem determination process because you do not have access to information about a data area, you need to contact your IBM Support Center. They may not necessarily tell you the format and contents, but they investigate the problem in the usual way, as described in IBM program support.