H06.11 Software Installation and Upgrade Guide

DSM/SCM and the H06.11 RVU
• The DSM/SCM H02 PVU (T6031H02) is supported for Integrity NonStop NS-series servers
only.
• A new type of hardware platform and selectable option, TNS/E, for Integrity NonStop
NS-series servers has been added to the Planner Interface (PI) screens. See the DSM/SCM
User’s Guide for configuration information.
• By default, the DSM/SCM H02 PVU is configured to manage OSS files. Check that OSS is
configured and started if DSM/SCM is set to manage OSS files. If not, the Apply can fail.
• CNFGINFO supports new system generation options for dynamic-link libraries (DLLs).
• Creating a SIT is not supported in H-series RVUs.
• Similar to G-series RVUs, you might have to update both the client and server-side SPRs.
For H06.11, the PI screen displays G02/H02 for the client side and H02 for the server side.
• As of G06.27, you can manage an H-series target system from a G-series host system.
However, you cannot currently manage a G-series target system from an H-series host.
• When you upgrade the client and server SPRs for DSM/SCM, you must also upgrade the
SWID product (T9298H02) at the same time to avoid a fingerprint or mismatched file problem.
For the H06.11 RVU, SWID is already installed.
DSM/SCM and Public DLLs
In H-series RVUs, DSM/SCM manages and controls the distribution, installation, and activation
of public DLLs on 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 in H-series RVUs, use the T6031H01 or later PVU. The
corresponding client version or Planner Interface must also be installed. For H06.11, the PVU
for the client is T6031G02/H02 and the PVU for the server side is T6031H02. (In H-series RVUs,
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 T6031H02 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 the client
version (Planner Interface) from ZDSMSCM 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.
Summary of Software Installation Tasks
To install software using DSM/SCM, perform these tasks:
Using DSM/SCM With the H06.11 RVU 23