Asynchronous Terminals and Printer Processes Configuration and Management Manual

Managing ATP6100 Using the
Subsystem Control Facility (SCF)
Asynchronous Terminals and Printer Processes Configuration and Management Manual—424280-003
6-41
TRACE LINE Command
Considerations for the TRACE LINE Command
•
If TO file-spec is specified, a new TRACE is initiated, unless file-spec is invalid, the
file cannot be opened, or a trace is already active for the ATP6100 process object
associated with the line. If TO file-spec is omitted, the TRACE command applies to
the trace currently in process, if any.
•
The keyword ALL selects all trace options.
•
If the trace file already exists, it is purged of data before the trace is initiated.
Examples of the TRACE LINE Command
The following command starts the trace of the line $ATPS1, puts the results in a file
named TRCFIL1, and selects all trace options:
->TRACE LINE $ATPS1,TO TRCFIL1,SELECT ALL
The following command starts the trace of the line $ATPS1, puts the results in a file
named TRCFIL2, and selects the L2 and CLBI trace options:
->TRACE LINE $ATPS1,TO TRCFIL2,SELECT (L2,CLBI)
The following command starts the trace of the line $ATPS1, puts the results in a file
named TRCFIL2, selects the ALL trace option, and specifies a BACKUP trace process:
->TRACE LINE $ATPS1,TO TRCBKUP,SELECT ALL,BACKUP
The following command stops the trace of the line $ATPS1:
->TRACE LINE $ATPS1,STOP
Note. Trace options can be specified as either keywords or corresponding numeric values.
SCF accepts a combination of keywords and numeric values within a TRACE command. Also,
numeric values are not verified by ATP6100—an undefined value has no effect and no warning
is issued.