OSI/AS SCF Reference Manual

Table Of Contents
OSI/AS Trace Facility
OSI/AS SCF Reference Manual424121-001
3-22
Trace Record Displays
Trace Record Displays
The rest of this section provides the following information:
Describes the format of the displays
Tells you how to get help when you have problems
Shows you samples of each type of trace record in the following order:
°
Trace records common to both the OSI manager process and the TAPS
processes:
°
Trace records for TAPS ASN.1 processes
°
Trace records for TAPS ACSE processes
°
Trace records for TAPS L6 processes
°
Trace records for TAPS L5 processes
The OSI/AS Configuration and Management Manual provides examples of some of the
OSI/AS trace record displays that are most important in troubleshooting.
Note. The formatted trace files that you will create may not appear exactly as documented in
this manual.
Trace records provide a mix of internal and user information and will reflect your network
configuration and the type of applications you are running.
Trace records are used for product development and maintenance as well as for tracking down
protocol problems in user applications.
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/AS can be read by the C20 or later version of
PTrace. Trace files generated by the C30 version of OSI/AS can only be read by the post-C20
version of PTrace.