NET/MASTER Management Services (MS) System Management Guide

Configuring Application Process Persistency
Configuring the Processing Environment
115414 NonStop NET/MASTER MS System Management Guide 11–45
As users log on to NonStop NET/MASTER MS, each logon becomes associated with
an available interactive user-supporting process (either NC or MS). Users are assigned
to processes in a circular fashion. (The SHOW PROCESS and SHOW USERS
commands enable users to determine the name of the process that is responsible for
processing the user’s workload.)
After all MS-supporting processes have 10 users associated with them, the NCP
dynamically starts an MS-supporting process to accommodate additional users,
provided that your configuration enables dynamic creation of MS-supporting
processes.
The following example illustrates the distribution of interactive user logons across
multiple CPUs. At a central operations site, approximately 20 operators are logged on
at any given time. Additional users log on and off intermittently, creating minor local
upsurges and downsurges in the workload. Suppose that you have the objective of
spreading the logons across each of the four CPUs available to NonStop
NET/MASTER MS:
In extended basic mode, configure three static MS processes to supplement the
workload processed by the NC process. Configure each process to start in a
different CPU.
In advanced mode, configure four static MS processes. Configure each process to
start in a different CPU.
The workload is spread across four processes, each in a different CPU. Each operator
logon is handled by a process in a circular fashion.
In extended basic mode, the NC process would support five interactive user
logons, and each of the three MS processes would support five interactive user
logons.
In advanced mode, each of the four MS processes would support five interactive
user logons.
You achieve optimum performance by defining one static MS process for each CPU
available to the NonStop NET/MASTER MS system. Alternatively, you can simply
estimate the number of concurrent interactive user logons and configure enough static
processes to support the estimated number efficiently.
Configuring
Application Process
Persistency
A persistent process is one that cannot restart itself after failure: that is, it relies on
another process to restart it. NonStop NET/MASTER MS application processes are
started as persistent processes. If a persistent process fails, the NCP starts a new copy
of the process.
It is important to understand two aspects of configuring application process
persistency. First, you cannot make an individual occurrence of a persistent
application process more or less persistent. However, you can configure NonStop
NET/MASTER MS with a combination of persistent application processes, so that the
functions collectively performed by NonStop NET/MASTER MS are likely to continue
despite process failure.