NET/MASTER Management Services (MS) System Management Guide

Running BK, EM, and NC Processes as Process Pairs
Configuring the Processing Environment
115414 NonStop NET/MASTER MS System Management Guide 11–49
If access to remote systems is important, configure an additional IS process. (A typical
configuration is NCP, NGM, SECEXIT, BK, EM, IS, IS, and MS.)
If availability to interactive user logons is important, configure an additional MS
process. (A typical configuration is NCP, NGM, SECEXIT, BK, EM, IS, MS, and MS.)
If both availability to interactive user logons and access to remote systems is
important, configure an additional MS and IS process. (A typical configuration is
NCP, NGM, SECEXIT, BK, EM, IS, IS, MS, and MS.)
CPU Allocation and
Persistency
As described earlier in this section, an application process runs in one CPU. You can
further enhance persistency by spreading application processes over multiple CPUs. If
one CPU fails, the function performed by the failed application process continues in
the other application process in the other CPU.
For example, in extended basic mode, do one of the following:
When using two NC processes, allocate one NC process to CPU 0 and the other
NC process to CPU 1.
When using one NC process and one BK, EM, IS, or MS process, allocate the NC
process to CPU 0 and the BK, EM, IS, or MS process to CPU 1.
In advanced mode, allocate one BK, EM, IS, and MS process to CPU 0 and the
additional BK, EM, IS, or MS process(es) to CPU 1.
When applied to application processes, the two numbers specified by the
PROCESSCPU operand of the PARAM command specify the first-choice and second-
choice CPU assignments for starting a process. When an application process starts, it
is started in the first-choice CPU (if available). If the CPU fails, the application process
is restarted in the second-choice CPU. Therefore, NonStop NET/MASTER MS may
not be optimally balanced after a CPU failure and restart.
Running BK, EM, and
NC Processes as
Process Pairs
All application processes are started by the NCP as persistent processes. BK, EM, and
NC processes can also run as process pairs. This subsection discusses the following
topics:
Starting a BK, EM, or NC process pair
Determining the BK, EM, or NC backup process
Recovering after BK, EM, or NC process pair failure
BK, EM, and NC process pairs in the NonStop NET/MASTER MS processing
environment
Starting a BK, EM, or NC
Process Pair
A BK, EM, or NC process stops running as a persistent process and starts running as a
process pair on the first occasion that an NCL process running in an NCL processing
environment within the BK, EM, or NC process starts a persistent NCL process. A
backup BK, EM, or NC process is created to ensure that the persistent NCL process can
be restarted if the BK, EM, NC, or NCL process fails. The BK, EM, or NC process
continues running as a pair when the persistent NCL process stops (ready to support
other persistent NCL processes).