NET/MASTER RMS Management and Operations Guide

BASERULE
Base Rulesets
12–4 115415 NonStop NET/MASTER RMS Management and Operations Guide
Customizing the Rule
It is strongly recommended that you change the volume on which you place the CPU
dump files to a volume other than $SYSTEM. The $SYSTEM volume is reserved for
system files, and you do not want to use up space by filling $SYSTEM with dump files.
RMS passes the name of the volume as the last parameter to ZRMSCPUN as follows:
ZRMSCPUN CPU &WORD5 dump-file-volume
The above command string is in the NCL Proc Name field on page 5 of the message
action rule definition panels. To use a different volume, change dump-file-volume
(for example, change $SYSTEM to $DATA1).
If you want to disable the dump, delete dump-file-volume from the NCL Proc
Name field.
You can also customize the rule by changing the execution limit of the NCL queue in
which the rule actions execute. Use the NCLQUEUE SET command from the OCS
command line to change the execution limit. See Section 3, “Planning for, Installing,
and Managing RMS,” for more information.
ZCPUUP ZCPUUP is a message action rule that acts in response to event number 100 from the
CPU subsystem. The rule rebalances the CPUs after reloading a failed CPU.
Message Delivery
The rule instructs the message handler to replace the original message (event number
100 from the CPU subsystem) by the following:
CPU0100 Process Up, CPU nn - REBALANCING SYSTEM
nn identifies the successfully reloaded CPU. The subject is nn (for example, 1).
Rule Actions
When a message triggers the rule, the message handler issues Peripheral Utility
Program (PUP) commands to rebalance the CPUs on your system. The commands are
passed to PUP using a user-specified IN file.
NCL Queue
The rule actions execute in the BASERULEZCPUUP NCL queue, which has a default
execution limit of 1.
Customizing the Rule
You should create your own IN file $SYSTEM.STARTUP.PUPPRI to reflect the load
balance requirements on your system. The message handler issues the following
command when a message triggers the rule:
OPSYS SEND TACL PUP /IN file-name /
The command string is in the Command Text field on page 5 of the message action
rule definition panels. If you do not use $SYSTEM.STARTUP.PUPPRI as the name of
your IN file, change file-name to the name of your file.