OSI/TS SCF Reference Manual

OSI/TS Trace Facility
OSI/TS SCF Reference Manual—424832-001
3-17
Getting Help
Additionally, the formats of individual trace records are subject to change with product
IPMs or with new software releases. Records (or fields within records) may be added or
deleted as necessary.
PTrace might not be able to display all data, for example, a complete DSM command
buffer, if the data is longer than the trace record size specified by the SCF TRACE
START command. The trace record size is shown in the trace header record.
Guidelines for the trace record size are provided in the considerations for the TRACE
command.
Trace files generated by the C21 version of OSI/TS can be read by the C20 or later
version of PTrace. Trace files generated by the C30 version of OSI/TS can only be read
by the post-C20 version of PTrace.
Getting Help
When using the SCF TRACE command to create a complete trace file that might be sent
to Compaq for analysis, issue the SCF TRACE command with the default select-spec
values (the default is ALL) to collect all information in the unformatted trace file. It is
recommended that you send the unformatted trace file, rather than a formatted PTrace
file.
Follow the standard procedures at your site for contacting the appropriate support
personnel. These procedures might involve contacting the local Compaq National
Support Center or your local Compaq Support representative. For information on
contacting a Compaq representative, refer to the Getting Help subsection in Section 4 of
the OSI/TS Configuration and Management Manual.
Trace Record Formats
A formatted trace file contains one trace header record followed by one or more trace
records.
Trace records are identified by type, subtype, and operation. Type and subtype describe
the format of the trace record and indicate what was happening in the code when the
trace information was taken. An operation might identify an I/O operation. In this case,
each operation will also be further qualified with the “request” or “response” suffix. An
operation might be just a single action like start a timer, or it could further qualify a
subtype, like a CR-TPDU specifies the type of TPDU.
If PTrace does not recognize the trace type, PTrace displays the contents of the data
buffer in hexadecimal.