ServerNet Cluster 6780 Operations Guide (G06.28+, H06.05+)

SCF Commands for SNETMON and the ServerNet
Cluster Subsystem
ServerNet Cluster 6780 Operations Guide525606-003
4-27
STOP Command
STOP Command
The STOP command terminates access to the ServerNet cluster subsystem in an
orderly manner. It stops ServerNet cluster services on the local system, terminates
ServerNet connections with other systems in the ServerNet cluster, and moves the
subsystem to the STOPPED state.
STOP is a sensitive command.
The STOP command syntax is:
OUT file-spec
causes any SCF output generated for this command to be directed to the specified
file.
FORCED
Currently, there is no difference between STOP SUBSYS and STOP SUBSYS,
FORCED.
Considerations
If the STOP SUBSYS command is entered correctly, the ServerNet cluster monitor
process generates an EMS message that reports the command, the time it was
executed, the terminal from which the command was entered, and the group and
user numbers of the user issuing the command.
Terminating access from the local system to the ServerNet cluster proceeds as
follows:
1. The ServerNet cluster monitor process sets the ServerNet cluster subsystem
state to STOPPING and logs the state change.
2. The ServerNet cluster monitor process informs each remote ServerNet cluster
monitor process that it is stopping.
3. The ServerNet cluster monitor process instructs each local processor to
terminate ServerNet connectivity.
4. When the processors have completed, this ServerNet cluster monitor process
moves the subsystem to the STOPPED state and logs the change.
5. The ServerNet cluster monitor process itself does not stop. It remains an active
process in the STARTED logical state.
Note. The ServerNet cluster monitor process (SNETMON) itself does not stop. It remains
running in the STARTED logical state.
STOP [ / OUT file-spec / ] SUBSYS $ZZSCL [, FORCED ]