NonStop S-Series Operations Guide (G06.27+)

Starting and Stopping the System
HP NonStop S-Series Operations Guide—522459-008
16-18
Stopping the System
You might able to automate the startup of many processes, lines, devices, and
applications. For example, you can use the SCF interface to the Kernel subsystem to
add process names to the system configuration database—typically monitor or
manager processes such as $ZEXP, the Expand manager process; $ZNET, the
Subsystem Control Point (SCP) process; or $ZPMON, the OSS monitor process.
Refer to the SCF Reference Manual for the Kernel Subsystem.
You also can automate your startup procedures by including commands in startup
command files that you invoke from a TACL prompt or another startup file. Startup
files contain a series of commands that automatically execute when the file is
executed. The NonStop S-Series Planning and Configuration Guide describes startup
files. Refer also to the SCF Reference Manual for G-Series RVUs. For some
techniques to make startup command files run as efficiently as possible, refer to
Reducing Shutdown Time on page 16-23.
Follow your site’s procedures for executing the system configuration and startup
command files and for starting up your application software.
Stopping the System
Stopping a system means halting each processor (terminating all processes running in
each processor) on the system in an orderly fashion. To prepare a system for a
planned outage and to stop the system, perform these tasks:
1. Preparing to Stop the System on page 16-19
2. Procedure to Stop the System Using OSM or TSM on page 16-20
Alerts
Before stopping a system:
•
Unless you stop a system in a careful and systematic manner, you can introduce
abnormalities in the system state. Such abnormalities can affect disk file
directories and can cause the processors to hang in an endless loop when you
attempt to load your system.
•
To maximize application availability, make stopping the system a planned event
whenever possible.
•
If you are planning to power off the system after stopping it, you must leave either
processor 0 or processor 1 running and have a TACL process running to issue the
SCF power-off command.
•
The TACL SPOOLER DRAIN subcommand stops the spooler in an orderly
manner. It is the only recommended way to stop the spooler.
•
If the system is a member of a ServerNet cluster, HP recommends that you first
remove the system from the cluster. For removal procedures, refer to the
ServerNet Cluster 6780 Operations Guide or (for ServerNet II or earlier cluster
configurations) the ServerNet Cluster Manual.