G06.30 Software Installation and Upgrade Guide

Overview of Installing G06.30
G06.30 Software Installation and Upgrade Guide—543764-002
1-8
Installing Required or Recommended SPRs Before
Installing a New RVU
HP recommends that the target systems be upgraded to at least the T6031ABZ
version of DSM/SCM before the host system is upgraded to this SPR.
Installing Required or Recommended SPRs Before Installing a
New RVU
Before installing G06.30, install required or recommended SPRs. An SPR could be
required for any of these reasons:
•
To prepare for fallback
•
To install a defect repair for a product that is required for a successful upgrade
•
To maintain interoperability for a product across a network
To determine which SPRs you should apply to your current RVU before you install
G06.30, see Section 3, Installing SPRs Before Upgrading to the G06.30 RVU.
To install SPRs using DSM/SCM, see Appendix A, Using DSM/SCM to Install SPRs.
Installing the G06.30 RVU Using DSM/SCM
1. Receive new software into the DSM/SCM Archive.
When software is received, the files from each product are stored in the DSM/SCM
Archive, a holding area for your software. File attributes are stored in the
DSM/SCM host database. Each time a new version of a product is received, only
changed files are placed in the Archive, and file attributes are updated in the Host
database.
2. Create a new software revision.
A software revision is a list of products stored in the DSM/SCM Archive that will be
built into a new software revision. A software revision can include a SUT, SPRs,
and third-party software. When you create a new software revision, DSM/SCM
selects the products in the SUT that are licensed for your site and replaces
previous versions of the products.
3. Build and apply the new software configuration revision.
The Build process creates an activation package containing all the products listed
in the new software revision. During the Apply process, the activation package is
transferred to the target system, and the new software is placed on the target
system’s subvolumes. When the Apply request is finished, a snapshot is
automatically created and returned to the Host.
4. Activate the new operating system image.
During the Build/Apply phase, DSM/SCM places product files in their target
subvolumes (TSVs) with temporary (fabricated) file names so that the new files do
not conflict with the file names of currently running programs. You run the
ZPHIRNM program on the target system to: