Installation and Upgrade Guide

Overview of Installing G06.24
G06.24 Software Installation and Upgrade Guide—528593-005
1-4
HP NonStop Server Software Requirements
•
SQL/MX Release 2.0 fallback SPRs. See Section 3, Installing SPRs Before
Upgrading to the G06.24 RVU.
•
A D46 product version of DSM/SCM on your host system before you install the
SUT. Appendix B, Installing the Latest DSM/SCM SPRs and Client Software
describes how to restore from tape and install the recommended D46 SPR of
DSM/SCM. The D46 DSM/SCM client and server version enable you to manage
OSS files.
°
If you are upgrading to the G06.24 RVU, download the most current client
version of DSM/SCM (T6031D46) from the ZDSMSCM subvolume after the
D46 new product version has been restored and activated from the SUT tape.
The DSM/SCM T6031D46^ABJ client software supports T6031D46^ABJ
server software and T6030/T6031D30^AAO and previous DSM/SCM server
software (including T6031D31). To install the DSM/SCM client, see
Appendix B, Installing the Latest DSM/SCM SPRs and Client Software.
°
Even if you installed the D46 product version update (PVU) introduced in
G06.18, you should install the new D46 T6031^ABJ SPR introduced in G06.24.
See Appendix B, Installing the Latest DSM/SCM SPRs and Client Software. If
you have to fall back to a pre-D46 T6031 product version of DSM/SCM, you
must run the FALLBACK macro available in T6031D46 and later product
versions. You can export the FALLBACK macro from the DSM/SCM Archive.
•
If you are running on a pre-G06.20 RVU, you must also install the Software
Identification (SWID) product (T9298AAJ) before receiving the SUT. See
Appendix B, Installing the Latest DSM/SCM SPRs and Client Software.
Note. All OSS SUT-based products with pax files must have the A7CINFO file in their distributed
subvolumes (DSVs) to be installed by DSM/SCM. Check the appropriate product softdocs and the
Interactive Upgrade Guide to ensure DSM/SCM installation is possible.
OSS products that are not released with an A7CINFO file in their DSVs can still be installed using
PINSTALL /COPYOSS. See the appropriate OSS manuals.
To ensure that OSS-managed files can be correctly restored in case of a fall back to an earlier RVU,
do not use the PINSTALL /COPYOSS utilities to install those OSS products that DSM/SCM has
installed on an OSS file system.
During the Build/Apply phase to manage OSS files, DSM/SCM indicates which OSS products in a
configuration are not DSM/SCM-enabled. For those OSS products, use PINSTALL/COPYOSS.