NET/MASTER Management Services (MS) System Management Guide

Balancing Static and DSNM Processes Among CPUs
Configuring the Processing Environment
11–60 115414 NonStop NET/MASTER MS System Management Guide
Configuring Process
Weight
As described earlier in this section in “PARAM Commands Used to Create a Process
Definition,” process weight refers to the resources that a dynamic process can
consume in a CPU that is available for the creation of dynamic processes. You can
configure process weight during or after NonStop NET/MASTER MS startup.
Configuring Process Weight During NonStop NET/MASTER MS Startup
As described earlier in this section in “PARAM Commands Used to Create a Process
Definition,” you use the PROCESSWEIGHT operand of the PARAM command in the
CONFIG file to initially configure the process weight of a dynamic process.
Configuring Process Weight After NonStop NET/MASTER MS Startup
After NonStop NET/MASTER MS startup, you can change dynamic process weight
using the PROCESS ALTER command with the WEIGHT operand. The change takes
effect when the NCP creates a new occurrence of the dynamic process. For example,
to change the weight of the dynamic process $Z002 from 5 to 20, use the following
command:
PROCESS ALTER=$Z002 WEIGHT=20
How CPU Weight and
Process Weight Factors
Interact
When the NCP receives a request to create a dynamic process, the NCP searches for a
CPU in which to create the dynamic process in the following order:
1. By using a running CPU with CPU weight greater than or equal to the process
weight of the dynamic process.
If a CPU can handle the request, the search stops: otherwise, the search for a CPU
continues.
2. By using a running CPU with CPU weight less than the process weight of the
dynamic process.
If a CPU can handle the request, the search stops: otherwise, the search for a CPU
continues.
3. By using any running CPU.
At least one CPU must be running for NonStop NET/MASTER MS to be running.
Note The NCP builds a circular list of the CPUs available on your Tandem system at NonStop NET/MASTER
MS startup (from 0 through the highest available CPU, and then back to 0). The NCP always starts in
CPU 0 when it initially searches for a CPU in which to create the first dynamic process required after
NonStop NET/MASTER MS startup. Thereafter, the NCP starts from the next available CPU and uses
the rules described above as it searches through the circular list.
This search order means that you cannot instruct dynamic processes to execute in
specific CPUs. However, by judicious CPU weight and process weight assignments,
you can influence how dynamic processes are assigned to CPUs.
This search order also means that the NCP will create a dynamic process in any
running CPU, if necessary, if the workload demands it. CPU weight and process