The FID for the SLIP user trace record is X'04'. The EID
is X'4006'.
| Offset |
Size |
Description |
|---|
| 0 (0) |
2 |
CPUID. |
| 2 (2) |
2 |
Extension number. |
| 4 (4) |
1 |
Continuation length. |
| 5 (5) |
2 |
Length of the user defined data. |
| 7 (7) |
variable |
User-defined data (specified through the TRDATA parameter on
the SLIP command). |
Note: - If the SLIP user requests registers to be placed in the SLIP user
record, they are the first field in the record.
- A length field of zero indicates that the user-defined data was
not available (for example, the data is paged out).
- The TRDATA parameter on the SLIP command specifies one or more
data ranges. The number of records needed to trace these ranges depends
on the size of the ranges specified. The trace contains a standard
plus (+) user record from the next range or a user record followed
by as many user records and user continuation records as needed to
trace the ranges specified. The header for each record contains the
CPUID and extension number to help correlate the output (extension
numbers apply only to user and user continuation records). When a
record is partially filled and the data from the next range will not
fit in the remaining space; the partially filled record is written
to the trace data set. Another user record is built, the extension
number is increased by one, and the continuation length is set to
zero. The data length and data is then copied into this record.
When
the length of the data from a range is greater than 249 bytes, the
excess data is put in user continuation records in the following manner.
The data length and first 248 bytes are put in a user record. After
writing that record a user continuation record is built. The extension
number is increased by one and the continuation length is set to the
number of bytes of data to be put in this record. If more than 251
bytes of data are left, 248 bytes are copied into record, and it is
written. User continuation records are built until all the data in
from that range is traced.