HP Integrity NonStop H-Series - Manual (Page 23)

Installing and Configuring Software
Use NonStop Software Essentials to install and manage new and revised software products from
HP or third-party vendors. HP delivers release version updates (RVUs) on a site update tape (SUT)
on one or more tapes or DVDs. SPRs are usually delivered on a backup tape or through a network
connection.
CAUTION: Software packages received into the archive must be as delivered from HP. Do not
overlay SPRs into product distribution subvolumes (DSVs) before receiving the software into the
archive.
NOTE: For H/J series systems where the SUT is delivered through CD/DVD, the IPSetup User's
Guide needs to be followed to place the files on the NonStop Systems. IPSetup starts the $ZRVU
process and thus helps NonStop Software Essentials to perform Receive Software activities.
You can choose when NonStop Software Essentials requests are executed, but you must perform
all requests in the specified order.
Receive the software into the software archive on your host system. NonStop Software Essentials
receives SPRs independently into the archive, then rolls up the SPRs when you use the Copy to
functionality. This allows NonStop Software Essentials to be able to show exactly which files
changed in which SPRs and allows you greater flexibility in managing configurations. To create
a list of the products to be installed, you use the Create new software revision functionality to select
from among software stored in the archive.
NOTE: When a Gxx SUT that contains both the heap manager products (T8431 and T1269) is
copied to the new software revision, the Heap Manager Selection dialog box is displayed. This
feature is supported only on systems running G06.29 and later G-series RVUs. After selecting the
desired heap manager product, click the Continue button to copy the SUT to the new software
revision. To cancel the Copy to operation, click the Cancel button.
A Build request readies the software to be placed on the target system by an Apply request. The
Build creates a new configuration revision that contains the product versions, an operating system
image, and relevant profile items such as the location of the target subvolume.
An Apply request places the configuration revision on the target system using temporary file names.
Guardian files for a target system are placed in a TSV. OSS files are placed in a target directory
location (TDL). A snapshot of the target’s new configuration is received into the host database to
update the host’s record of the target’s software configuration.
From there the software is renamed, put in its proper functioning location, and then activated. You
must run ZPHIRNM before performing a system load if one is required. You use ZPHIRNM to
rename changed files from their temporary file names to their real names. ZPHIRNM renames all
the prior files that are being replaced to temporary file names. You can use these files later if you
need to back out a revision. ZPHIRNM is run independently of all other processes, so you can
minimize application downtime and schedule it for a time most convenient for your work
environment.
The temporary file naming allows files to be applied while the system is running without interfering
with the existing files on the running system. If the system needs to be backed out to the previous
revision, ZPHIRNM is run during the Backout process to give the actual file names back to the files
from the previous revision. The renaming process reduces application downtime and allows for a
quick backout by rerunning ZPHIRNM and specifying the previous SYSnn.
Figure 1-2 (page 24) is an overview of the software configuration management process in a typical
NonStop Software Essentials usage pattern, applied to networked and non-networked systems.
Detailed procedures are included later in this manual.
Installing and Configuring Software 23