NET/MASTER Management Services (MS) System Management Guide

Balancing Static and DSNM Processes Among CPUs
Configuring the Processing Environment
115414 NonStop NET/MASTER MS System Management Guide 11–59
Configuring CPU Weight During NonStop NET/MASTER MS Startup
During NonStop NET/MASTER MS startup, the PARAM CPUWEIGHT command is
used in the CONFIG file.
If the command is not present in the CONFIG file, the NCP determines the CPUs that
exist, assumes that all are available for use by NonStop NET/MASTER MS, and
configures each CPU for maximum availability.
If the command is present in the CONFIG file but does not configure all available
CPUs, the NCP determines the additional CPUs, assumes that they are available for
use by NonStop NET/MASTER MS, and configures them for maximum availability.
If the command is present in the CONFIG file and configures all CPUs, you must
configure at least one CPU with a value greater than 0 for NonStop NET/MASTER MS
to be able to start.
For example, if you have a system with eight CPUs and you want to restrict dynamic
processes to CPUs 0 through 5, use the following PARAM commands:
PARAM CPUWEIGHT=(0,100)
PARAM CPUWEIGHT=(1,100)
PARAM CPUWEIGHT=(2,100)
PARAM CPUWEIGHT=(3, 50)
PARAM CPUWEIGHT=(4, 50)
PARAM CPUWEIGHT=(5, 50)
PARAM CPUWEIGHT=(6, 0)
PARAM CPUWEIGHT=(7, 0)
Configuring CPU Weight After NonStop NET/MASTER MS Startup
After NonStop NET/MASTER MS startup, you can enter the command from the OCS
command input line or from any NCL procedure, if your authority level is equal to or
greater than 9.
This command immediately changes the current CPU weight of the specified CPU. It
does not update the configuration file, and the weight assigned during NonStop
NET/MASTER MS startup is unchanged. Therefore, if NonStop NET/MASTER MS is
stopped and restarted, the weight assigned during NonStop NET/MASTER MS
startup, specified in the CONFIG file, is again assigned to the CPU.
If you change the current CPU weight to 0, no new processes are started in that CPU.
Processes running in the specified CPU are not affected by a change in CPU weight,
even when the change means that a process is left running in a CPU whose weight is
changed to 0. The change takes effect when a new process starts.