ServerNet Cluster 6780 Operations Guide (G06.29+, H06.06+, J06.03+)

Controlling ServerNet Cluster Processes
ServerNet Cluster 6780 Operations Guide—525606-004
2-3
Starting the Message Monitor Process (MSGMON)
Starting the Message Monitor Process
(MSGMON)
For details about adding MSGMON to the configuration database, see the ServerNet
Cluster 6780 Planning and Installation Guide.
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)
You might have to abort MSGMON in these two cases:
•
During installation of a T0294 software product revision (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 with
SCF ALTER PROCESS $ZZKRN.#MSGMON. Normally, you should not need to
alter any of the MSGMON process configuration attributes if you configured
MSGMON with the TACL macro documented in the ServerNet Cluster 6780
Planning and Installation Guide.
Aborting MSGMON on a node does 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 cannot:
•
Bring up remote IPC connectivity to any processor that is reloaded in the cluster
•
Bring up IPC connectivity to any new node that is added to the cluster
•
Automatically repair any failed remote IPC connections.
Expand-over-ServerNet lines to any new node that is added to the cluster while
MSGMON is not running are not brought up either.
To abort MSGMON on the local system, use the SCF ABORT PROCESS command:
> ABORT PROCESS $ZZKRN.#MSGMON
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.