G06.27 Software Installation and Upgrade Guide
Installing the Latest DSM/SCM SPRs and Client
Software
G06.27 Software Installation and Upgrade Guide—540067-001
B-14
Recovery for Problems While Installing the G02 PVU
of DSM/SCM
The latest SWID SPR for G06.27:
VPROC - T9617G03 - (07 AUG 2003) SYSTEM \IT Date 24 AUG 2005, 02:02:49
Copyright 2003 Hewlett-Packard Development Company, L.P.
$SPRS.R9298G02.SWID
Binder timestamp: 06JUL2005 00:28:23
Version procedure: T9298G02_30AUG2005_06JUL2005G02
Target CPU: TNS, TNS/R
AXCEL timestamp: 06JUL2005 00:28:26
Recovery for Problems While Installing the
G02 PVU of DSM/SCM
If you encounter problems while installing the D46 version of DSM/SCM, see the
following information and the DSM/SCM User’s Guide.
If NonStop Errors Are Displayed
Starting with the D30 PVU of DSM/SCM, the IPM6031 TACL macro is run
automatically during STARTSCM when DCSM/SCM detects that the DSM/SCM
servers or database managers have changed. The IPM6031 TACL macro also ensures
that the TAEXE and CBEXE programs are secured correctly.
Install the DSM/SCM Client From ZDSMSCM
Starting with the G06.18 RVU, the T6031G02 DSM/SCM client software is shipped
only on the SUT and not on the Installer CD. The ZDSMEXE file that is in ZDSMSCM
subvolume is the client version that is an exact match to the server software in
ZDSMSCM.
If you are using DSM/SCM to manage OSS file options, you must install the DSM/SCM
client software.
DSM/SCM T6031G02 client software supports DSM/SCM server software (including
T6031D31). If you have to fall back, you can use the newly installed client software but
you should revert back to the previous DSM/SCM PVU.
Alert (DSM/SCM T6031G02 Client)
Do not attempt to use DSM/SCM T6031G02 client software until you have first installed
the T6031G02 PVU on your host system. See Table 3-1, DSM/SCM Client and Server
Compatibility, on page 3-5.
Note. Before you begin, back up your current DSM/SCM folder to save the configuration
information and the Planner Interface version.
Check that unnecessary PC programs are not running before you begin the DSM/SCM client
installation and that no DSM/SCM Build or Applies are in progress.