H06.05 Software Installation and Upgrade Guide

H06.05 Software Installation and Upgrade Guide541762-003
B-1
B
Installing SWID, DSM/SCM PVU, and
Planner Interface (PI) Client Software
Alerts
Determine the Product Version of DSM/SCM on the Host System and Determine
the Product Version of DSM/SCM on the Client.
Save the current configuration database. (See Save the Current Configuration File
(CONFxxyy) on page 3-3).
Keep the startup TACL windows, the EMS Event Stream window, and the
DSM/SCM client interface windows open whenever you are performing a
Build/Apply. Otherwise, Build/Apply errors will result.
If you receive an error indication in the Request Status window, you might have to
reinitiate the Build/Apply. See the DSM/SCM Messages Manual to learn the nature
and severity of the problem.
Determine the Product Version of DSM/SCM on the Host System
To determine which product version of DSM/SCM is currently installed on your system,
use the VPROC command to determine the product version of TAEXE (Apply product
of DSM/SCM) and CBEXE (Build product of DSM/SCM).
At a TACL prompt, enter:
> volume $dsmscm_vol.ZDSMSCM
> vproc taexe
> vproc cbexe
Note.
For Integrity NonStop NS-series servers, you must have installed both the DSM/SCM SPR
and the corresponding client version before you receive an RVU SUT. For
H06.05, all
newly shipped Integrity NonStop NS-series servers will have the latest DSM/SCM SPR
installed. The latest DSM/SCM client version is available only on the SUT unless you have
ordered new system consoles.
Always install the latest SWID PVU at the same time you install a new DSM/SCM PVU to
avoid a fingerprint or mismatched file problem. (DSC/SCM uses SWID to determine if a file
has changed by a method called fingerprinting. If an existing file has a different fingerprint
from a newer file, the newer version replaces the existing file.) For H06.05, your newly
shipped Integrity NonStop NS-series server will have the latest SWID SPR.