ServerNet Cluster 6780 Planning and Installation Guide (G06.24+, H06.03+)

Configuring MSGMON, SANMAN, and SNETMON
ServerNet Cluster 6780 Planning and Installation Guide—527301-004
E-2
TACL Macro
TACL Macro
The ZSCCONF macro automates the process of adding MSGMON, SANMAN, and
SNETMON to the system-configuration database. The macro:
•
Detects the number of processors currently loaded and prompts you to confirm this
number (if your system has fewer than four processors)
•
Aborts and deletes the MSGMON, SANMAN, and SNETMON processes if they are
already present
•
Returns error messages if the processes could not be successfully deleted
•
Adds the processes using a processor list that is appropriate for the system size
•
Starts MSGMON, SANMAN, and SNETMON and attempts to start the ServerNet
cluster subsystem
Run the ZSCCONF Macro
1. Log on using the super ID (255, 255). The macro will not run successfully if you
use another user ID.
2. From the $SYSTEM.ZSUPPORT subvolume, run the ZSCCONF macro:
> RUN ZSCCONF
3. When the macro finishes, check that the SCF state of $ZZSCL is in the STARTED
state:
-> STATUS PROCESS $ZZKRN.#ZZSCL
4. Start $ZZSCL if needed:
-> START PROCESS $ZZKRN.#ZZSCL
Note. Before using the macro:
•
You must log on using the super ID (255, 255) in order to run the macro successfully.
•
Do not run the macro on a node that is currently a member of a ServerNet cluster.
MSGMON, SANMAN, and SNETMON will be aborted, and the connection to the cluster
will be lost temporarily.
•
The macro is intended as an example and might not be appropriate for all systems.
Note. Do not run the ZSCCONF macro on a node that is currently a member of a ServerNet
cluster. MSGMON, SANMAN, and SNETMON will be aborted, and the connection to the
cluster will be lost temporarily.
The ZSCCONF macro leaves the ServerNet cluster subsystem (also known as ServerNet
cluster services) in the STOPPED state. If you use the Add Node to ServerNet Cluster action
from the OSM Service Connection, the action automatically starts the subsystem. Otherwise,
you must use the SCF START SUBSYS $ZZSCL command to start the subsystem.