X25AM Configuration and Management Manual

SCF Commands for the X25AM Subsystem
X25AM Configuration and Management Manual—523424-004
4-52
Command Syntax for the TRACE Command
LINE line-name
designates the line to be traced. If you omit line-name, SCF traces the assumed
line (for information about the ASSUME command, see the SCF Reference Manual
for G-Series RVUs or SCF Reference Manual for H-Series RVUs).
STOP [ , BACKUP ]
discontinues the trace currently in progress. If you specify BACKUP, SCF stops
only the trace of the backup process.
BACKUP
specifies that the backup process should receive the trace request. The object
must be running as a process pair if you use this syntax. If the primary process is
being traced when a takeover by the backup process occurs, the trace of the
process continues. However, in this case, most events being traced before the
process switch are no longer traced because the process being traced is no longer
the primary process. If you omit BACKUP, SCF assumes the primary process.
COUNT count
specifies the number of trace records that you want to capture. count is an integer
in the range -1 through 32767. If you omit COUNT or if count equals -1, records
accumulate until you stop the trace.
NOCOLL
indicates that the trace collector process should not be initiated. Some subsystems
might select this option automatically.
PAGES pages
designates how much space, in pages, you want to allocate in the extended data
segment used for tracing. You can specify PAGES only when you initiate a trace.
pages is an integer in the range 4 through 1024 or equal to 0 (zero). If you omit
PAGES or if pages equals 0, SCF assumes the default value of 64 pages.
RECSIZE size
specifies the length of the data in the trace data records. size is an integer in the
range 16 through 4050 or equal to 0 (zero). The length of the trace header, which
is 8 bytes, is not included in size. If RECSIZE is omitted or if size equals 0, the
default value of 120 bytes is assumed.
Using the default value of 120 bytes in a CLIP trace could result in data being
truncated. When starting a CLIP trace, RECSIZE should be the larger of 150 bytes
or the L3 packet size plus 4 to avoid CLIP trace data from being truncated. In order
to capture all Level 2 events, RECSIZE should be 256.