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

Starting and Stopping the System
HP NonStop S-Series Operations Guide—522459-008
16-23
Reducing Shutdown Time
Reducing Shutdown Time
An important component of a planned outage is the time required to start and stop your
applications, devices, and processes. These general techniques can help reduce the
time required to start up and shut down these objects:
•
Write efficient startup and shutdown command files.
•
Use parallel processing to distribute startup and shutdown processes across
multiple processors.
•
Investigate and use product-specific techniques for fast startup and shutdown.
Write Efficient Startup and Shutdown Command Files
A good way to start and stop objects and processes in your system is to use startup
and shutdown command files. Command files are supported by TACL and by many
subsystems for NonStop S-series servers. You can improve the efficiency of your
startup and shutdown command files by applying these techniques:
•
Use command file syntax that executes quickly.
•
Avoid manual intervention to ensure that command files execute quickly
Command File Syntax
The syntax used in command files affects the time it takes for them to execute. To
ensure that your command files execute quickly:
•
Avoid using wild-card characters
•
Use single-line commands instead of multiple-line commands
A wild card is a character—typically an asterisk (*) or a question mark (?)—used to
match any character or series of characters. When you use wild-card characters in
your command files, execution time is increased because the system must look up
names in a table. By using explicit names instead of wild-card characters, you can
shorten execution time and allow for commands to execute in parallel.
This PATHCOM START command uses a wild-card character to start all of the TERM
objects defined in the PATHMON configuration file:
= START TERM *
This PATHCOM START command uses explicit names to start all of the TERM objects
defined in the PATHMON configuration file:
= START TERM (TERM1, TERM2, TERM3, TERM4, TERM5, TERM6)
Note. When using explicit names, you must revise your command files whenever a
configuration change occurs. Therefore, you should balance the time it takes to update
configuration files against the savings in startup or shutdown time.