Interpreting the unformatted global trace table

The formatted trace table contains information copied from the unformatted resident trace table, which is always included in the non-summary section of the dump data set.

A resident trace table contains fixed-length, 64-byte records. A given Db2 event is recorded in a single record if there are no more than five event-data items; otherwise, they are recorded in two adjacent records. The first record, which might be the only record, contains a long header and up to five event-data items. The second record, if there is one, contains a short header and any remaining data items (up to a maximum of six items in the second record). The short header of the second record contains only the time-of-day stamp, which matches the time-of-day stamp in the first record. The second doubleword is X'FFFFFFFF00000000', and the six doublewords contain the data items.

The contents of the first and second record are shown in the following tables.

Table 1. Unformatted Db2 trace record content for first record
Decimal offset Hex offset Length (decimal) Field Description
0 0 8 Time of Day. The TOD clock. This field is zero if the TOD clock value is not available. In a formatted trace table, this field follows the eye-catcher TOD.
8 8 0.5 Number of event-data items in the record or record pair. This field does not appear in the formatted trace table.
8.5 8.5 0.5 Indicator of the type of event. (Possible values are shown below.)
9 9 1 RMID. One-byte ID of the reporting resource manager. In a formatted trace table, this field follows the eye-catcher EID.
10 A 2 Two-byte event number, unique for the specific resource manager. When combined with the RMID, this number makes a unique trace event identifier.
12 C 1 Internal function code. In a formatted trace table, this field follows the eye-catcher FUNC.
13 D 1.5 Twelve-bit primary ASID (the address space containing the data). In a formatted trace table, this field follows the eye-catcher ASID. Any data addresses in the item list point to objects in this address space.
14.5 E.5 1.5 Twelve-bit ASID of the caller of the CSECT that invoked the trace facility. In a formatted trace table, this field follows the eye-catcherRET.
16 10 4 Four-byte return address of the caller (from register 14).
20 14 4 Four-byte address of the EB control block that was current at the time of the event. In a formatted trace table, this field follows the eye-catcher EB.
24 18 varies A series of up to five 8-byte data items (such as addresses or values) associated with the event. The total number of items in the record, or record pair, is given in the second field of the trace record (offset X'08'). In a formatted trace table, this field follows the eye-catcher DATA.
Table 2. Unformatted Db2 trace record content for second record
Decimal offset Hex offset Length (decimal) Field description
0 0 8 Time of Day. The 8-byte TOD clock. This field is zero if the TOD clock value is not available. In a formatted trace table, this field does not appear.
8 8 4 Doubleword of X'FFFFFFFF00000000'
16 18 varies A series of up to six 8-byte data items (such as addresses or values) associated with the event. The total number of items in the record, or record pair, is given in the second field of the first record.
Table 3. Db2 trace tag values and meanings
TAG value (hex) Tag Name In Formatted Trace Table Definition
00 blank Used when none of the other predefined codes in this table is applicable
01 RMENTRY Resource manager functional entry point, invoked via RMRQ
02 RMEXIT Resource manager functional exit point
03 RAENTRY Resource Application request functional entry point, invoked via RARQ
04 RAEXIT Resource Application request functional exit point
05 BKNBCST Begin notification sequence
06 ENDBCST End notification sequence
07 Reserved Reserved
08 Reserved Reserved
09 CALLENTRY Resource manager functional entry point, invoked via CALL
0A CALLEXIT Resource manager functional exit point
F0 Not applicable in Db2-issued trace tables Start trace control record, valid for GTF destination only
F1 Not applicable in Db2-issued trace tables Stop trace control record, valid for GTF destination only