H06.04 Software Installation and Upgrade Guide

Overview of Installing the H06.04 RVU
H06.04 Software Installation and Upgrade Guide—541607-001
1-7
Upgrading the DSM/SCM Client (Planner Interface) and
the T6031H01 PVU
installed and configured. However, the OSS root fileset ($ZPNS) must be in the started
state; otherwise, the Build/Apply fails.
Upgrading the DSM/SCM Client (Planner Interface) and the
T6031H01 PVU
To upgrade the DSM/SCM client, if you did not order new system consoles, the
DSM/SCM client version must be downloaded from the ZDSMSCM subvolume. (If you
have acquired new system consoles, the most up-to-date DSM/SCM client is already
installed.) To download from ZDSMSCM the client version (Planner Interface) to a
separate PC console or your current console, follow the client or Planner Interface
installation instructions in the DSM/SCM User’s Guide or Appendix B, Installing SWID,
DSM/SCM PVU, and Planner Interface (PI) Client Software.
Installing a New H06.04 SUT Using DSM/SCM
HP automatically installs and configures DSM/SCM and your specific products before
shipping the Integrity NonStop NS-series server. Perform these tasks:
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, if Expand-connected.
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: