SNACONTROL STOP
MPE documents | |
 Complete PDF | |
| Table of Contents | |
| Index |
Syntax
SNACONTROL STOP;NODE=NodeName[;TYPE=StopType]
Use
SNACONTROL STOP can be issued from a session, a job, a program, or in break. Pressing [BREAK] has no effect on this command.
Parameters
- NodeName
Conditionally required. The name of the active SNA node you want to stop. The name can be up to eight alphanumeric characters long; the first character must be alphabetic.
If only one SNA node is active, this parameter is optional: If you do not include it, the active node is stopped. If more than one node is active, this parameter is required: If you do not include it, a list of all configured SNA nodes is displayed, but no node is stopped; you can then reissue this command with the appropriate node name.
- StopType
How SNA Transport is to stop the node:
K = (Kill) The node is stopped immediately. To the users of the node, this is like a link failure. The remote system is not notified that SNA Transport is stopping.
CAUTION: Data can be lost in a kill shutdown.P = (Protocol) SNA Transport notifies the SNA services that it is stopping. Each service interrupts sending and receiving all active data sets, and tries to stop the LU-LU sessions. SNA Transport then stops the LU-SSCP sessions and the PU-SSCP session, but it does not stop the node until all SNA Transport users have terminated their sessions.
Q = (Quiesce) The node is stopped in an orderly way. SNA Transport notifies the SNA services that it is stopping. Each service completes sending and receiving all active data sets. As the LUs become inactive, the services stop the LU-LU sessions, and SNA Transport stops the LU-SSCP sessions. Then, SNA Transport shuts down the PU-SSCP session.
Description
SNACONTROL STOP stops an SNA node and all activity on the node: link-level tracing, SNA Transport intrinsic tracing, SNA Transport node tracing, and any SNA services that are running (and their associated tracing). Once all sessions are closed, a logging message is generated and SNA Transport begins releasing its resources. When all resources are released, SNA Transport logs a "SHUTDOWN COMPLETE" message and terminates.
Examples
SNACONTROL STOP;NODE=PU8100F Node PU8100F is to be stopped in an orderly way (a quiesce). A quiesce is done because no StopType was specified. SNACONTROL STOP;TYPE=K The only active node is to be immediately stopped (a kill). Note that if more than one node was active, this command would not be valid: A list of configured nodes would be displayed, and the command would have to be reissued with the proper NODE=NodeName parameter included.|
SNACONTROL STATUS |
SNACONTROL STOPSESS |