HP NonStop NS How Process Persistence Affects Configuration and Startup, Tips for Startup Files

Creating Startup and Shutdown Files Investigate Product-Specific Techniques

Investigate Product-Specific Techniques

Some products provide commands that reduce the time required to start up or shut down their services. Familiarize yourself with the products and applications that run on your system to identify time-saving techniques for speeding startup and shutdown operations. Refer to the relevant documentation for each product.

For example, the HP NonStop TS/MP product provides the COOL START option and the SHUTDOWN2 command to shorten startup and shutdown times, respectively. Using the COOL START option, rather than COLD START, to restart an existing transaction-processing system is much faster. The SHUTDOWN2 command is faster and more reliable than the SHUTDOWN command. Both of these techniques are described in the TS/MP System Management Manual.

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.

HP Integrity NonStop NS-Series Operations Guide—529869-005

16-11