NonStop S-Series Planning and Configuration Guide (G06.25+)

Planning for System Configuration
HP NonStop S-Series Planning and Configuration Guide—523303-015
15-5
Subsystem Control Facility (SCF)
Each subsystem manager or monitor process is started by the $ZPM persistence
manager process at system load and has the following functions:
•
Creates I/O processes and other manager processes within the subsystem
•
Configures subsystem objects such as adapter hardware and the ServerNet
addressable controllers (SACs) supported by those adapters
•
Identifies the names of processes that must be reserved at system load
•
Monitors its processes to immediately re-create any process that has terminated (if
it was configured to be persistent)
Each configuration manual listed in Generic Process Manuals on page E-5 describes a
subsystem, the objects the subsystem supports, and how to configure those objects.
Generic Processes
Generic processes can be created by the operating system or by a user. Examples of
generic processes created by a user are an HP program, a third-party program, or a
user-written program that you configure to be controlled by the operating system.
When the system is started, all generic processes that are configured to be persistent
are started automatically by the $ZPM persistence manager or by the subsystem
manager, which is started by $ZPM.
For more information about generic processes, refer to the SCF Reference Manual for
the Kernel Subsystem.
Making Important Processes Persistent
You can make important system processes, such as the Expand manager process or
the Subsystem Control Point (SCP) process, start automatically at system load and be
persistent (that is, restart automatically if stopped abnormally) by creating them as
generic processes in the system configuration database and specifying the
AUTORESTART parameter. Refer to the NonStop S-Series Hardware Installation and
FastPath Guide.
Types of System Configuration Files
On systems running G-series RVUs, most I/O processes are not prebuilt by
SYSGENR. Instead, the subsystems place information about these processes in the
system configuration database.
On systems running G-series RVUs, the SYSnn.OSCONFIG file contains only
Software Problem Isolation and Fix Facility (SPIFF) and Software ID (SWID) records.
On systems running G-series RVUs, the system configuration database files are stored
on the $SYSTEM.ZSYSCONF subvolume, independent of the SYSnn subvolume that
the operating system is running on.