ServerNet Cluster Manual

SCF Commands for SNETMON and the ServerNet
Cluster Subsystem
ServerNet Cluster Manual520575-003
8-22
Considerations
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.
6. Only the subsystem state changes are logged. The individual path state
changes are not logged.
7. On remote systems, when the ServerNet cluster monitor processes are notified
of the STOP, they instruct their local processors to terminate ServerNet
connectivity with the stopping system. These remote ServerNet cluster monitor
processes then log the node disconnection to the event log.
Example
The following SCF command stops ServerNet cluster services on the local system,
terminates ServerNet connections with other systems in the cluster, and moves the
subsystem to the STOPPED state:
> STOP SUBSYS $ZZSCL
TRACE Command
The TRACE command:
Starts a trace operation on a ServerNet cluster monitor process
Alters trace parameters set by a previous TRACE command
Stops a previously requested trace operation
Is a sensitive command