OSI/AS Configuration and Management Manual

Troubleshooting Guide

OSI/AS Configuration and Management Manual—424119-001

8-7

Running the TRACE Command

To start a trace, use the TRACE command and specify the desired trace options. While

tracing is on, you can issue the TRACE command to modify COUNT, RECSIZE, or any

of the SELECT specifications. The following example starts a trace of the process

TAPS1, collects only information related to the Layer 6 activity of that process, and

writes the trace information to a file named TRACE1:

TRACE PROCESS $TAPS1, TO TRACE1, SELECT (L6), RECSIZE 4050

To stop a trace, use the TRACE command with the STOP option. The following

example stops the trace started in the previous example:

TRACE PROCESS $TAPS1, STOP

Running PTrace

To start PTrace interactively, enter PTrace at the TACL or SCF prompt. You may also

enter other PTrace commands, such as the name of the file containing the trace

information, as follows:

PTrace FROM TRACE1

In addition, you can specify a file to store your PTrace commands and the output, as

follows:

LOG TO $MARS.MYSTUFF.TRACELOG

To stop the PTrace utility and return to TACL or SCF, enter the following:

EXIT

Note. The formatted trace files that you create may not appear exactly as shown in this

manual.

Trace records provide a mix of internal and user information and, therefore, 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

and with new software releases; records (or fields within records) may be added or deleted.