NonStop NS-Series Operations Guide (H06.03+)

Creating Startup and Shutdown Files
HP Integrity NonStop NS-Series Operations Guide—529869-001
16-5
$ZHOME Alternative
°
Never specify $ZHOME for the INFILE for a process. The $ZHOME process
returns the FEINVALOP error (file-system error 2) in response to any read
operation.
•
Generic processes started by the $ZPM persistence manager inherit
$YMIOP.#CLCI as the HOMETERM, INFILE, and OUTFILE unless these attributes
are changed in the configuration record for the generic process. HP recommends
that you configure most NonStop Kernel and system-level generic processes to
use $ZHOME for the HOMETERM and OUTFILE.
$ZHOME Alternative
Instead of $ZHOME, you might want to use the optional NonStop Virtual Hometerm
Subsystem (VHS) product if both of the following conditions are true:
•
The processes you are configuring cannot handle error responses returned if
$YMIOP.#CNSL or $YMIOP.#CLCI is not available.
•
The process must perform read operations to the device.
Example Command Files
This section describes and shows examples of command files that can be used to start
up and shut down the server:
•
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.
•
These examples are for a system whose configuration has been changed from the
factory-installed configuration. Your system’s initial configuration will differ from
these examples.
The startup files in this section assume that the objects they start have already
been added to the system configuration database.
•
The IP addresses used in this section are examples only. If you use the example
files described in this section on your system, you must change the IP addresses
in these examples to IP addresses that are appropriate for your LAN environment.
•
The configuration track-ID for the SWAN concentrator used in the example files,
X001XX, is also an example.
If you use the example files described in this section on your system, you must
change the configuration track-ID used in these examples to the actual
configuration track-ID assigned to your SWAN concentrator.