Troubleshooting the SWAN Concentrator and WAN Subsystem

Tracing a Communications Line
Tracing a communications line is initiated using the SCF TRACE command. Tracing
enables you to see the history of a communications line, including significant points in the
internal processing of the traced entity.
For tracing to be an effective, fault-finding tool, make sure you follow these guidelines:
Always trace both ends of a communications path.
Ensure that all traces for a particular problem are taken at the same time.
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-megabyte or
4-megabyte file is generally sufficient for all but the longest or most work-intensive
traces.
For Expand lines, 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.
Trace files can be displayed using the commands available in the PTrace program. For
information about PTrace, see the PTrace Reference Manual. For information about the
SCF TRACE command, refer to the configuration and management manual for the
communications subsystem you want to trace.