J06.04 Software Installation and Upgrade Guide

Creating a SIT is not supported in J-series RVUs.
You might need to update both the client and server-side SPRs. For J06.04, the PI screen
displays G02/H02 for the client side and H02 for the server side.
As of G06.27, you can manage a J-series target system from a G-series host system. However,
you cannot currently manage a G-series target system from a J-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 J06.04 RVU, SWID is already installed.
WARNING! If an J06.03 or later host system is used to perform DSM/SCM builds for a target
system that is running an H-series release prior to H06.12, you must install the appropriate T0431
(OSBUILD) SPR for that target system before performing the build. If this is not done, then the
DSM/SCM Sysgen (OSBUILD) will fail. The build will complete successfully if it is being done for
an H06.12 or later system.
The appropriate T0431 SPRs are:
Target System RVUSPR
H06.10 and H06.11T0431H01^AAK
H06.09T0431H01^AAH
H06.08T0431H01^AAN
H06.07T0431H01^AAM
H06.05 and H06.06T0431H01^AAL
Any J-series RVU attempting to build an H-series RVU prior to H06.12 must install these SPRs.
DSM/SCM and Public DLLs
DSM/SCM manages and controls the distribution, installation, and activation of public DLLs on
NonStop BladeSystems the same way that it does on H-series systems. Public DLLs are installed on
the H-series and J-series target systems in their own subvolume.
To manage OSS files in J-series RVUs, use the T6031H01 or later PVU. The corresponding client
version or Planner Interface must also be installed. For J06.04, the PVU for the client is
T6031G02/H02 and the PVU for the server side is T6031H02.
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
Using DSM/SCM With the J06.04 RVU 15