SNAX/XF and SNAX/APN Configuration and Management Manual
SCF Commands for SNAX/XF and SNAX/APN
SNAX/XF and SNAX/APN Configuration and Management Manual—425836-006
13-125
STOP Command
SEL [ NOT ] state
directs the command to stop only objects in the specified state (if NOT is omitted)
or only objects not in the specified state (if NOT is specified).
Valid object states are ABORTING, DEFINED, DIAGNOSING, STARTED,
STARTING, STOPPED, STOPPING, SUSPENDED, SUSPENDING, and
UNKNOWN. The object states are described in Section 12, Objects for SNAX/XF
and SNAX/APN.
The SEL option is valid only for SESSION objects.
Considerations
When a STOP LINE command is issued, the local PU (#ZNT21) is always stopped
as long as no local LUs are open or in session. This is true even if the STOP
command subsequently fails because one or more remote PUs are not stopped.
A STOP command for the TLOGMGR LU causes the TLOGMGR LU to be placed
in the STOPPED state if there are no active sessions between the TLOGMGR LU
and the ILOGMGR LU.
For the SESSION object type, sess-name is a 16-digit fully qualified procedure
correlation identifier (FQPCID). Users can find FQPCIDs by issuing any of the
following commands:
NAMES LU, SUB ALL
NAMES LU, SUB SESSION
STATUS, SUB ALL for the LINE, PU, and LU objects
Examples for SNAX/XF
->STOP LINE $SNAP2
->STOP LINE $SNAP4,SUB ALL
->STOP LINE ($SNAP6,$SNAP7),SUB PU
->STOP LU $SNAP1.#LU1
->STOP LU $SSCP.#LU2
->STOP PU $SNAP1.#PU1
->STOP PU $SNAS1.#PU2,SUB ALL
->STOP SESSION $SNAP1.#LU1
->STOP SUBSYS $SSCP,SUB ALL
Examples for SNAX/APN
->STOP LINE $APN2
->STOP LINE $APN4,SUB ALL
->STOP LINE ($APN6,$APN7),SUB PU