Asynchronous Terminals and Printer Processes Configuration and Management Manual
Table Of Contents
- What’s New in This Manual
- About This Manual
- 1 Configuration Quick Start
- 2 Overview of the ATP6100 Subsystem
- 3 Configuring the ATP6100 Subsystem
- 4 Printer Profiles and Default Modifiers
- 5 Terminal Profiles and Default Modifiers
- 6 ManagingATP6100Usingthe SubsystemControlFacility(SCF)
- 7 PTrace Facility for ATP6100
- A ATP6100 Subsystem Error Messages
- B SCF Command Summary for ATP6100- ABORT LINE Command
- ABORT SU Command
- ACTIVATE SU Command
- ALTER LINE Command
- ALTER SU Command
- INFO LINE Command
- INFO SU Command
- LOAD LINE Command
- START LINE Command
- START SU Command
- STATS LINE Command
- STATS SU Command
- STATUS LINE Command
- STATUS SU Command
- STOP LINE Command
- STOP SU Command
- SUSPEND SU Command
- SWITCH PROC Command
- TRACE LINE Command
- VERSION PROC Command
 
- C Moving to G-Series or H-Series RVUs
- Glossary
- Index

Managing ATP6100 Using the 
Subsystem Control Facility (SCF)
Asynchronous Terminals and Printer Processes Configuration and Management Manual—424280-003
6-38
TRACE LINE Command
TRACE LINE Command
The TRACE LINE command initiates, modifies, or terminates trace mode on ATP6100 
lines. Using TRACE, you can request capture of target-defined data items, alter trace 
parameters, and end tracing. TRACE LINE is a sensitive command.
An SCF trace produces a trace file that can be displayed using PTrace commands. 
The trace file is created by SCF. The PTrace utility is described in Section 7, PTrace 
Facility for ATP6100.
Command Syntax for the TRACE LINE Command
The TRACE LINE command has the following syntax: 
OUT file-spec
causes any SCF output generated for this command to be directed to the specified 
file.
LINE line-name 
designates the object to be traced. If you omit line-name, SCF traces the 
assumed object (see the SCF Reference Manual for G-Series RVUs or SCF 
Reference Manual for H-Series RVUs for details about the ASSUME command).
STOP [ , BACKUP ]
discontinues the trace currently in progress on the primary process. If you specify 
BACKUP along with STOP, only the backup process trace is stopped.
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.
TRACE [ / OUT file-spec / ] LINE line-name
 { , STOP [ , BACKUP ] }
 { [ , BACKUP ]
 [ , COUNT count ]
 [ , NOCOLL ]
 [ , PAGES pages ]
 [ , RECSIZE sizes ]
 [ , SELECT select-spec ]
 [ , TO file-spec ]
 [ , WRAP ]... }










