H06.03 Software Installation and Upgrade Guide

Overview of Installing the H06.03 RVU
H06.03 Software Installation and Upgrade Guide540066-002
1-6
Public DLLs and DSM/SCM
CNFGINFO supports new system generation options for dynamic link libraries
(DLLs).
Creating a SIT is not supported on H-series.
Similar to G-series RVUs, you might have to update both the client and server-side
SPRs. For H06.03, the PI screen displays G01/H01 and the server side H01.
Management of an Integrity NonStop NS-series server’s target system from a
NonStop S-series host system is not available for H06.03.
You should also install the SWID product (T9298H01) before receiving the SUT
whenever you have a new T6031 PVU. For the H06.03 RVU, SWID is already
installed.
Public DLLs and DSM/SCM
For H-series, DSM/SCM manages and controls the distribution, installation, and
activation of public DLLs on HP Integrity NonStop NS-series servers similarly to the
way DSM/SCM handles public SRLs on NonStop S-series systems. Public DLLS are
installed on the H-series target systems in their own subvolume.
Starting with the G06.18 RVU, a new configuration file, A7CINFO, is introduced for
managing OSS files. To manage OSS files on H-series, use the T6031H01 PVU. The
corresponding client version or Planner Interface must also be installed. For H06.03,
the product version update (PVU) for the client is T6031G01/H01 and the PVU for the
server side is T6031H01. (For H-series, the T6030 PV has been obsoleted and does
not appear on the SUT.)
DSM/SCM and OSS
When performing a Build/Apply, ensure that the setting of the Manage OSS Files
option matches with your target system. If the target system is not to use OSS, you
must uncheck the OSS files option box before beginning a Build request. If the box is
left checked, OSS is included by the Build request. The OSS root fileset needs to be
configured and started before files can be copied into the OSS file system by
DSM/SCM. For OSS users who request HP to install OSS, it is assumed that OSS is
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.