ServerNet Cluster Manual

Managing a ServerNet Cluster
ServerNet Cluster Manual—520575-003
5-28
Starting the Message Monitor Process (MSGMON)
ServerNet cluster. SCF commands for configuring, starting, stopping, and displaying
information about the SCL subsystem SUBSYS object are described in Section 8, SCF
Commands for SNETMON and the ServerNet Cluster Subsystem.
Starting the Message Monitor Process (MSGMON)
Adding the message monitor process (MSGMON) to the configuration database is
described in Section 3, Installing and Configuring a ServerNet Cluster. To run
MSGMON after adding it but before the next system load, or after stopping it by using
the SCF ABORT PROCESS $ZZKRN.#MSGMON command, use the SCF START
command:
> START PROCESS $ZZKRN.#MSGMON
Aborting the Message Monitor Process (MSGMON)
To abort MSGMON on the local system, use the SCF ABORT PROCESS command:
> ABORT PROCESS $ZZKRN.#MSGMON
There are two cases in which you might have to abort MSGMON:
•
During installation of a T0294 SPR that includes a new version of MSGMON. In
this case, follow the installation instructions in the SOFTDOC for that SPR.
•
Before you can alter one or more MSGMON process configuration attributes via
SCF ALTER PROCESS $ZZKRN.#MSGMON. Normally, you should not need to
alter any of the MSGMON process configuration attributes, as long as you have
configured MSGMON with the TACL macro documented in Appendix E.
Aborting MSGMON on a node will not change the state of ServerNet Cluster IPC
connectivity and Expand-over-ServerNet lines to and from that node. However, while
MSGMON is not running, the node will not be able to bring up or automatically repair
remote IPC connectivity. This includes bringing up remote IPC connectivity to any
processor that is reloaded in the cluster, bringing up IPC connectivity to any new node
that is added to the cluster, and automatically repairing any failed remote IPC
connections. Expand-over-ServerNet lines to any new node that is added to the cluster
while MSGMON is not running will also not be brought up.
Note. In this section, the message-system monitor process ($ZIMnn) is referred to as
MSGMON. The symbolic name for the MSGMON generic process is assumed to be
MSGMON, which also is the recommended symbolic name.
Note. Normally, you should not need to abort MSGMON—even if a system is no longer a
member of a ServerNet cluster.