NonStop NS-Series Operations Guide (H06.12+)

How Process Persistence Affects Configuration and Startup
When the system is started, all processes that are configured to be persistent are started
automatically by the persistence manager ($ZPM) or by the subsystem manager, which is started
by $ZPM.
For example, when the system is started, the WAN subsystem manager automatically starts all
WAN I/O processes (IOPs) that were started before the system was shut down. However,
communications lines and paths must be started manually by the operator.
To make important system processes start automatically at system load and be persistent (that
is, restart automatically if stopped abnormally), you should create them as generic processes in
the system configuration database. See the Integrity NonStop NS-Series Hardware Installation
Manual.
For more information about persistence and the $ZPM persistence manager, see the SCF Reference
Manual for the Kernel Subsystem.
Tips for Startup Files
HP recommends that you specify “N” for the read access portion of the file security attribute
(RWEP) for your startup files to allow the files to be read by any user on the network. For example,
you might secure these files “NCCC.”
The sequence in which you invoke startup files can be important. Some processes require other
processes to be running before they can be started. Be sure to indicate the order in which your
startup files are to be run.
Because the TCP/IP configurations are not stored in the configuration database, they are not
preserved after system loads. Therefore, TCP/IP stacks must be configured as well as started
each time the system is started. This is only true for conventional TCP/IP.
Startup File Examples
You can implement the system startup sequence with a collection of startup files, each with a
specific purpose. HP recommends that you invoke the startup files in this order:
1. Startup file for the system, to be invoked after the CIIN file is invoked
2. Startup files for the system software
3. Startup files for the subsystems
4. Startup files for the communications lines
5. Startup files for the applications
See Section 15, Starting and Stopping the System for detailed instructions on the startup procedure.
For information about automating disk processes upon startup, see the Integrity NonStop
NS-Series Planning Guide.
NOTE: Examples and sample programs are for illustration only and might not be suited for
your particular purpose. HP does not warrant, guarantee, or make any representations regarding
the use or the results of the use of any examples or sample programs in any documentation. You
must verify the applicability of any example or sample program before placing the software into
production use. For more information, see “Example Command Files” (page 175).
System Startup File
The following example shows a partial command file that starts up the system software and
invokes other startup files.
After the commands in the CIIN file have been executed and the initial system startup sequence
is complete, the local operator invokes this file by entering the following TACL command:
How Process Persistence Affects Configuration and Startup 181