SLIP user trace record

The SLIP user record represents a SLIP trap match when the SLIP command specifies ACTION=TRACE or ACTION=TRDUMP and TRDATA=parameters.

SLIP USR    CPU..... hhhh     EXT..... hhhh     CNTLN... hh
      hhhh  hhhhhhhh hhhhhhhh hhhhhhhh hhhhhhhh | cccccccccccccccc |

CPU hhhh

Processor ID.

EXT hhhh

Extension number.

CNTLN hh

Continuation length.

hhhh

Length for the single range in the SLIP command. If hhhh is zero, either the range was not available or the range was not valid, so that GTF did not collect data for the range. GTF would consider the range not valid if, for example, the ending range address precedes the beginning range address.

hhhhhhhh hhhhhhhh hhhhhhhh hhhhhhhh | cccccccccccccccc |

User-defined data fields that are specified by TRDATA on the SLIP command. The length and data fields may be repeated.

For a SLIP command, the trace contains as many user records and user continuation records as needed to trace the data ranges specified in the TRDATA parameter on the SLIP command. The header in each record contains the processor ID and the extension number. When a record is filled enough so that the next data range cannot fit, GTF writes the partially filled record to the GTF trace table. GTF builds another record; its extension number is increased by one and the continuation length is set to zero.

When the length of data from a range is greater than 249 bytes, the excess data is put in user continuation records. After writing the SLIP USR record, GTF builds a user continuation record. GTF increases the extension number by one and sets the continuation length to the number of bytes of data to be put in the continuation record. If more than 251 bytes of data are left, GTF copies 248 bytes into the record and places it in the GTF trace table. GTF builds user continuation records until all the data from a range is traced.