NET/MASTER Management Services (MS) System Management Guide

PARAM Commands Used to Create a Process Definition
Configuring the Processing Environment
115414 NonStop NET/MASTER MS System Management Guide 11–7
Note PARAM operands that specify process type and logical name reset the values of PARAM operands that
specify process attributes to default values. Nevertheless, for clarity, Tandem recommends that you
explicitly define each process using all applicable operands.
The PROCESSOBJECT
Operand
Whenever you configure a process in the CONFIG file, you must specify the name of
the program file from which a process is created. Use the PROCESSOBJECT operand
to specify the name of the program file of the process you want to start. Specify
PROCESSOBJECT as a valid file name. Table 11-1, earlier in this section, lists program
file names for NonStop NET/MASTER MS processes.
For example, to specify the name of a GMM process program file, include the
following command in a process definition:
PARAM PROCESSOBJECT=$DATA.ZNNM.NGM
This operand is mandatory for all process definitions. It typically appears first in a
process definition.
The PROCESSCLASS
Operand
Use the PROCESSCLASS operand to explicitly define the class of a static or dynamic
application process (BK, EM, IS, MS, or NC). All application processes can be created
from the same application process program file, which you can duplicate or rename as
you wish. Using the PROCESSCLASS operand to specify BK, EM, IS, MS, or NC in an
application process definition creates a process from the program file that performs
the BK, EM, IS, MS, or NC function, respectively.
For example, to create a process that performs only the BK function of the program file
(a BK process), include the following command in the process definition:
PARAM PROCESSCLASS=BK
This operand is optional for all application processes, and does not have a default
value. If you omit this operand from an application process definition, the NCP uses
the file name specified by the PROCESSOBJECT operand to determine the class of the
application process (see “Configuring and Starting Application Processes by Using
Process Definitions,” later in this section, for more information).
The PROCESSCPU
Operand
Use the PROCESSCPU operand to assign the number of the preferred CPU in which a
process is to execute. Specify PROCESSCPU as two integers, separated by a comma,
from 0 through 15. The two integers should be different. The operand is ignored if
applied to dynamic processes (discussed later). The operand takes the following form:
PARAM PROCESSCPU=( cpu1 , cpu2 )
When applied to DSNM processes and single static processes, PROCESSCPU specifies
the first-choice and second-choice CPU assignments for starting a process. If cpu1 is
available, the NCP starts the process in cpu1 . If cpu1 is unavailable, the NCP
attempts to start the process in cpu2 . If cpu2 is unavailable, the NCP starts the
process in the next available CPU. A CPU’s relative availability is determined in part
by the weight assigned to it: its CPU weight (see “Influencing How Dynamic
Processes Are Balanced Among CPUs,” later in this section, for more information).