NET/MASTER Management Services (MS) System Management Guide

Configuring Static and Dynamic Application Processes
Configuring the Processing Environment
11–16 115414 NonStop NET/MASTER MS System Management Guide
Configuring Static and
Dynamic Application
Processes
As indicated in Table 11-1, there are five classes of NonStop NET/MASTER MS
application processes. Each application process class has either a static or dynamic
presence. The presence of an application process refers to the permanency of its
existence in the NonStop NET/MASTER MS processing environment. This subsection
discusses the following topics:
Static presence and static processes
Dynamic presence and dynamic processes
Starting application processes by using file names on disk
Configuring and starting application processes by using process definitions
Searching for static and dynamic processes
Exceeding recommended capacity limitations
Static Presence and Static
Processes
An application process with static presence, a static process, is designed to be always
present in the NonStop NET/MASTER MS processing environment.
A static process is initially started during NonStop NET/MASTER MS startup. If a
static process fails, the NCP restarts the process using the current configuration of the
failed process.
A static process is designed to remain in the processing environment from NonStop
NET/MASTER MS startup to shutdown. Fluctuations in workload do not affect the
creation or cessation of static processes by the NCP.
If you want the processing environment to contain a specified minimum number of
application processes, you should configure NonStop NET/MASTER MS to start the
specified application processes as static processes.
Dynamic Presence and
Dynamic Processes
An application process with dynamic presence, a dynamic process, is designed to be
present as required in the NonStop NET/MASTER MS processing environment.
A dynamic process is initially started during NonStop NET/MASTER MS startup. If a
dynamic process fails, the NCP does not necessarily start another dynamic process to
replace it.
A dynamic process does not necessarily remain in the processing environment from
NonStop NET/MASTER MS startup to shutdown. Fluctuations in workload affect the
creation and cessation of dynamic processes by the NCP.
If the workload diminishes to a level that no longer requires a dynamic process, the
dynamic process remains available for a predetermined time. If no additional
workload is dispatched to the dynamic process, the NCP stops the dynamic process.
Conversely, if the workload increases to a level that exceeds the capacity of the present
processing environment, the NCP starts additional dynamic processes using the
current configuration of the running process. NonStop NET/MASTER MS has no
architectural limits to the number of dynamic processes it can start.