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

Starting and Stopping the System
HP NonStop S-Series Operations Guide—522459-007
16-19
Alerts
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.
Preparing to Stop the System
You must stop all applications, devices, and processes in an orderly fashion before you
stop a system. You might be able to automate the shutdown of lines, devices, and
applications by including commands in one or more shutdown command files that you
invoke from either a TACL prompt or another shutdown file. Shutdown command files
contain a series of commands that automatically execute when the file is executed.
The NonStop S-Series Planning and Configuration Guide describes command files.
For some techniques to make shutdown command files run as efficiently as possible,
refer to Reducing Shutdown Time on page 16-24.
•
When you stop Pathway applications, all TCP objects begin shutdown (shutting
down TERM objects and then themselves) in parallel. New work is disallowed. The
PATHMON process logs the start and completion of SHUTDOWN2. It does not
log status messages during shutdown.
•
When you stop DSM/SCM, the CNFGINFO server process, the Pathway
environment for DSM/SCM, the alternate EMS collector $ZPHI, and TCP/IP
processes for DSM/SCM all stop, as this example shows:
STOP CNFGINFO server process $ZPHC
STOP DSM/SCM Pathway system $YPHI
PATHCOM $YPHI;SHUTDOWN !,WAIT
$Z02H: TCP TCP-H, STOPPED
$Z02H: TCP TCP-T, STOPPED
STOP DSM/SCM Alternate EMS Collector $ZPHI