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-9
ABORT SU Command
Considerations for the ABORT LINE Command
•
The SEL option is not supported.
•
If you are terminating both a line and its subordinate subdevices (for example, with
the SUB ALL option), SCF halts the subdevices first and then halts the line.
•
The ABORT command is rejected with an error if the line is in the DIAGNOSING
state.
•
A warning is returned if the line is in the STOPPED state.
•
All application OPENs are aborted when an ABORT command is sent.
•
When you use the ABORT command, all activities being performed by the line
come to an abrupt halt, and all outstanding requests are canceled.
Examples of the ABORT LINE Command
The following SCF command aborts a line named $ATPS1:
- > ABORT LINE $ATPS1
The following SCF command aborts all the subdevices associated with the line but
does not abort the line:
- > ABORT LINE $ATPS1,SUB ONLY
The following SCF command aborts all the subdevices and the line:
- > ABORT LINE $ATPS1,SUB ALL
ABORT SU Command
The ABORT SU command terminates the activity of the subdevice as quickly as
possible. The activities that were being performed by the subdevice are stopped
abruptly. All outstanding requests are canceled and the subdevice is placed in the
STOPPED state. ABORT SU is a sensitive command.
Command Syntax for the ABORT SU Command
The ABORT SU command has the following syntax:
OUT file-spec
causes any SCF output generated for this command to be directed to the specified
file.
ABORT [ /OUT file-spec / ] SU subdevice-name