X25AM Configuration and Management Manual

SCF Commands for the X25AM Subsystem
X25AM Configuration and Management Manual—523424-004
4-25
Considerations for the DELETE Command
Considerations for the DELETE Command
•
A subdevice must be in the STOPPED state before it can be deleted. For example,
to stop and then delete a subdevice, use the following commands:
-> STOP SU $SIP2.#term
-> DELETE SU $SIP2.#term
•
If you use the object-type LINE, you must also use the SUB option and set to
SUB ONLY, which indicates that all the subdevices subordinate to the named line,
but not the line itself, are to be affected by the command.
•
X25AM does not support the SEL option.
•
X25AM supports the SUB option only for the LINE object type.
DISCONNECT Command
The DISCONNECT command breaks the connection between two or more subdevices.
If the subdevice presently has a call established, DISCONNECT will force a clear
request to be sent and the call will be cleared. This is a sensitive command.
Command Syntax for the DISCONNECT Command
Syntax:
OUT file-spec
causes any SCF output generated for this command to be directed to the specified
file.
SU su-name
designates the subdevice to be disconnected. If you omit su-name, the assumed
subdevice is disconnected (for information about the ASSUME command, see the
SCF Reference Manual for G-Series RVUs or SCF Reference Manual for H-Series
RVUs).
Examples of the DISCONNECT Command
The following command breaks the connection between an assumed object and an SU
named $X25P1.#TERM1:
-> DISCONNECT SU $x25p1.#term1
Consideration for the DISCONNECT Command
•
X25AM supports the use of only the first su-name; X25AM does not support the
use of more than one su-name.
DISCONNECT [ / OUT file-spec / ] [ SU su-name ]