Expand Configuration and Management Manual (H06.21+, J06.10+)

Troubleshooting
Expand Configuration and Management Manual — 529522-013
20 - 30
Tracing
•
If the data rate is high, or if the trace is expected to run for many hours, preallocate
the file space for the trace file using the File Utility Program (FUP). A 3- or 4-
megabyte file is generally sufficient for all but the longest or most work-intensive
traces.
•
Gather a $NCP trace even if you don’t think the problem involves $NCP. It is
preferable to have too much rather than too little information.
Tracing $NCP
To start a trace of $NCP, use this command:
TRACE PROCESS $NCP, TO $file_name, SELECT ALL, WRAP, RECSIZE 500
To stop the trace, use this command:
TRACE PROCESS $NCP, STOP
$file_name specifies the name of the file to which the trace records will be written.
Tracing a Path or Single Line
To start a trace of a path or a single-line Expand line-handler process, use this
command:
TRACE PATH $device_name, TO $file_name, SELECT ALL, WRAP
To stop the trace, use this command:
TRACE PATH $device_name, STOP
$device_name specifies the device name of the path logical device or single-line
Expand line-handler process. $file_name specifies the name of the file to which the
trace records will be written.
Tracing a Line in a Multi-Line Path
To start a trace of a line that is part of a multi-line path, use this command:
TRACE LINE $device_name, TO $file_name, SELECT ALL, WRAP
To stop the trace, use this command:
TRACE LINE $device_name, STOP
$device_name specifies the name of the line logical device. $file_name specifies
the name of the file to which the trace records will be written.
Note. A TRACE PATH command will also trace all lines in a multi-line path, unless a TRACE
LINE command has already been issued for one or more lines in the path.
Note. Trace files can be displayed using the commands availa
ble in the PTrace program. For
more information on the PTrace, see the PTrace Reference Manual. For more information on
the SCF TRACE command, see Section
15, Tracing.