NonStop S-Series Hardware Installation and FastPath Guide (G06.28+)

Creating Startup and Shutdown Files
HP NonStop S-Series Hardware Installation and FastPath Guide—541880-001
13-9
Tips for Startup Files
Comment -- for the startup TACL before issuing this command (see the
Comment -- Start Terminal Emulator command under the File menu). This SCF
Comment -- command must be the last command in this file, because the TACL
Comment -- process creates displays a prompt and attempts to read from
Comment -- $YMIOP.#CLCI, blocking other processes from writing to this
Comment -- device.
SCF /NOWAIT, OUT/ START PROCESS $ZZKRN.#CLCI-TACL
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.
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 $ZPM persistence manager 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 like 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), you should create them
as generic processes in the system configuration database. See Section 12, Online
Configuration Tasks.
For more information about persistence and the $ZPM persistence manager, see the
SCF Reference Manual for G-Series RVUs.