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

5 Managing Software With NonStop Software Essentials
HP periodically issues new and revised software products for your NonStop systems. NonStop
Software Essentials is used to plan and install software on both local and distributed systems. From
a host system, you can control the installation and configuration of the software on all your systems,
local or remote, network-connected or not.
This chapter provides an outline of the basic software management steps used to upgrade software
running on a NonStop system. Each step links to the subsequent chapter that contains the detailed
information and procedures needed to perform these tasks. Additional help in performing tasks is
available within the online help for NonStop Software Essentials and the other NonStop software
management tools. The process of upgrading NonStop system software typically includes these
steps:
1. Receive Software – the act of receiving software packages into the archive involves copying
the software packages from their tape or disk subvolumes into the archive on the host system.
This process is described in
Chapter 6: “Receiving and Managing Software Packages” .
2. Create a Software Revision – identifies a set of products in the archive to be used to update
the software configuration on a NonStop system. This process is described in
Chapter 7:
“Creating and Managing Software Revisions” .
3. Build and Apply the New Configuration Revision – typically, you perform the build and apply
in a single step, as described in
Chapter 8: Primary Build and Apply Process . That chapter
also points to additional information for when the Apply process has to be done separately.
4. Activate the New Software on the Target System – the key activity in the activation process is
using ZPHIRNM to rename the software product files from temporary file names assigned
when they are applied on target system (so as not to interfere with any existing versions of
the software and minimize downtime for applications) to the correct names. The activation
process is described in
Chapter 9: “Activating New Software on a Target System” . and
Chapter 10: Renaming Product Files Using ZPHIRNM .
5. Chapter 11: Loading the System
NOTE: Managing Software to Avoid a System Load: NonStop Software Essentials requires a
system load whenever the OSIMAGE changes. However, to avoid system downtime, you can
reinitialize DSM/SCM without performing a system load when:
• For some SPRs, DSM/SCM assumes the OSIMAGE changed when it is unchanged.
• You modify the CONFTEXT file for comments only.
• You perform a backout to a previous configuration and use an identical configuration for a
Build/Apply.
TIP: To install and manage software on multiple NonStop systems with identical configurations,
see Chapter 17: “Simplified Installation and Management of Multiple Identical NonStop Servers
(Cloning)” .
Activating the New Software on the Target System
The sequence of steps involved in the activation process can vary depending on the system, the
products involved, the type of Build/Apply; the basic process involves:
• Prepare for activation: NonStop Software Essentials generates standard instructions for
activating software, depending on the type of Build/Apply, but those instructions can also be
modified when planning the configuration by adding simple notes or copying information
76 Managing Software With NonStop Software Essentials