Startup File Examples; System Startup File - HP NonStop NS-series Operation Manual

Creating Startup and Shutdown Files

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
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

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:
> OBEY $SYSTEM.STARTUP.STRTSYS
Comment -- This is $SYSTEM.STARTUP.STRTSYS
comment -- Start the server for labeled tape processing.
ZSERVER / NAME $ZSVR, NOWAIT, PRI 145, CPU 0 / 1
ZSERVER / NAME $ZSVR, NOWAIT, PRI 145, CPU 1 / 0
MEDIACOM ALTER TAPEDRIVE *, NLCHECK OFF
Comment -- If you have used SCF to start a persistent Subsystem
Comment -- Control Process (SCP) process pair, you do not need an
Comment -- explicit SCP command to start $ZNET, unless you load the
Comment -- system from a different CONFIG file.
Comment -- All SCF commands are routed through the SCP process.
Comment -- routes each request to the appropriate communication
Comment -- management process (such as Expand or SNAX).
Comment -- If you have not configured SCP as a persistent generic
Comment -- process, remove the commenting from the following SCP
Comment -- command and start SCP as a nonpersistent process pair.
Comment -- SCP / NAME $ZNET, NOWAIT, PRI 199, TERM $ZHOME, OUT $ZHOME, &
Comment -- CPU 0/1; AUTOSTOP -1
HP Integrity NonStop NS-Series Operations Guide —529869-005
for detailed instructions on the
Example Command Files
16 -12
Startup File Examples
on page 16-4.
$ZNET