H06.13 Software Installation and Upgrade Guide

B Installing SWID, DSM/SCM PVU, and Planner Interface
(PI) Client Software
NOTE:
For 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.13, all newly shipped 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. (DSM/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.13, your newly shipped NonStop NS-series server will have the latest SWID SPR.
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)” (page 62)).
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
If your VPROC commands do not display the following versions, install the latest H02 DSM/SCM
product version as described in “Copy (RESTORE) the H02 DSM/SCM Product Version to Disk (If
Necessary)” (page 126):
This example shows the ABQ product version update of DSM/SCM after DSM/SCM has been
activated for H06.07. (Bold lettering is used to show the VPROC command and the latest version):
\DRP08.$DSMSCM.ZDSMSCM 2> vproc cbexe
VPROC - T9617H01 - (01 OCT 2004) SYSTEM \DRP08 Date 12 May 2006, 18:20:02
Copyright 2004 Hewlett-Packard Development Company, L.P.
$DSMSCM.ZDSMSCM.CBEXE
Binder timestamp: 17NOV2005 15:59:49
Version procedure: S7032H06^01OCT2004^SWARCCP^H01
Version procedure: T6031H02_01NOV2005_16DEC05ABQ
Target CPU: UNSPECIFIED
OCA timestamp: 16DEC2005 16:06:21
\DRP08.$DSMSCM.ZDSMSCM 3> vproc taexe
124 Installing SWID, DSM/SCM PVU, and Planner Interface (PI) Client Software