H06.03 Software Installation and Upgrade Guide

H06.03 Software Installation and Upgrade Guide—540066-002
4-1
4
Installing a SUT for the H06.03 RVU
Installing a new RVU or a SUT involves these DSM/SCM tasks:
1. Receive New Software Into the Archive on page 4-2
2. Create a New Software Revision on page 4-6
3. Build and Apply the New Software Revision on page 4-11
Alerts for Installing a SUT
Do not use this procedure to upgrade more than one Integrity NonStop NS-series
servers at a time or to install SPRs. For SPRs, see Appendix A, Using DSM/SCM to
Install SPRs.
Before you install a SUT or RVU, these requirements must be met:
•
When managing OSS files with DSM/SCM, check that the OSS Root Name Server
$ZPNS is started and running on the DSM/SCM Target. (See Create a New
Software Revision on page 4-6.) The volume where the SYSnn is being placed
must be activated as $SYSTEM to install the OSS files. See Appendix B in the
Open System Services Management and Operations Guide, or if using EasySetup,
see Section 1 in the Open System Services Installation Guide.
•
Save the configuration database. See Save the Current Configuration File
(CONFxxyy) on page 3-3.
•
Verify your system operations. See Verify System Processes on page 3-3.
•
Update, if necessary, the system console.
•
Obtain a user name and password authorized to use the DSM/SCM Planner
Interface. See the DSM/SCM User’s Guide for more information about configuring
which users are allowed to use DSM/SCM and which tasks they are permitted to
perform.
•
Check that the OutsideView Startup TACL ($YMIOP.#CLCI) and EMS Event
Stream windows are open. These windows must remain open while DSM/SCM is
performing a Build/Apply; otherwise, Build/Apply errors result.
Note. Safeguard aliases are case-sensitive, and they must be entered exactly when you
log into DSM/SCM.
You can add a Safeguard alias anytime Safeguard is running.
Before using an existing alias for DSM/SCM, check that Safeguard is started. Aliases are
available only while Safeguard is running.