NonStop Operations Guide for H-Series and J-Series RVUs

$ZHOME
The $ZHOME process is a process pair that provides a reliable home terminal to which processes
can perform write operations. The $ZHOME process can be used by processes that must write to
the system console but do not require a response.
$ZHOME is preconfigured on your system by the CONFBASE file. $ZHOME is a generic process
that is part of the SCF Kernel subsystem. Note the following about the configuration of $ZHOME:
• The $ZHOME process is configured with $YMIOP.#CLCI as its HOMETERM, INFILE, and
OUTFILE.
• Because $ZHOME acts as a reliable home terminal designed to interact with the system
console, $YMIOP.#CLCI, HP recommends that you do not change its configuration. Most
important:
◦ Do not specify $ZHOME for the INFILE, OUTFILE, or HOMETERM for the $ZHOME
process.
◦ 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 is configured with its INFILE, OUTFILE, and HOMETERM set to $YMIOP.#CLCI. Messages
written to $ZHOME will appear on the $YMIOP.#CLCI window if the Startup TACL window
“Opening Startup Event Stream and Startup TACL Windows” (page 196)is open and paused. When
the $YMIOP.#CLCI window is closed, connectivity is lost and $ZHOME will then write the message
to $0. Specifically, the $ZHOME process writes the messages to its configured OUTFILE, which
by default is $YMIOP.#CLCI. If it gets an error writing to the OUTFILE, it switches to the collector
$0, which is hard-coded.
$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 system:
• 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.
202 Creating Startup and Shutdown Files