Installation and Upgrade Guide

Installing the Latest DSM/SCM SPRs and Client
Software
G06.24 Software Installation and Upgrade Guide—528593-005
B-3
Before You Begin Installing the Software
Identification (SWID) SPR
Before You Begin Installing the Software
Identification (SWID) SPR
If you are upgrading from a pre-G06.20 RVU, besides restoring T6030D31 and
T6031D46, you must also upgrade the Software Identification (SWID) (T9298D40AAK)
product at the same time to avoid a problem with ZPHIRNM renaming hybrid SRLs to
fabricated names. (With the introduction of dynamic-link libraries (DLLs) for TNS/R
systems in G06.20, NSKCOM (T5838) provides new commands to NLD (T6017) so
that public SRLs are built as hybrid DLL-SRL objects.)
If you are on a G06.20 RVU or later, you do not need to restore the SWID product
before receiving the SUT. See Alerts in this appendix.
Alerts
•
If you are on a pre-G06.20 RVU, besides restoring R6030D31 and R6031D46, you
must also receive R9298D40 in the DSMSCM Archive when you build the new
configuration. A new SWID SPR (T9298AAK) is introduced in G06.24, but you do
not need to restore and receive the SWID SPR if you are running a G06.20 RVU or
later. See Verify That SWID Is Installed on page B-17.
•
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 4-1).
•
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.
Note. If you do not restore SWID, and you are run the G06.24 RVU and perform another
Build/Apply with the previous pre-G06.20 SWID that was used to build the hybrid SRLs, and
you do not require a system load, the DSM/SCM fingerprint file will be different. As a result:
•
A new set of SRLs is created.
•
When the ZPHIRNM is complete, the open SRLs are renamed to fabricated names.
Note. Until the T6031ABE, or later, SPR of DSM/SCM is installed, you must select the
Receive-all-files option on all software inputs into the DSM/SCM Archive whether or not
you want to manage OSS files. When the T6031ABE, or later, SPR is applied, you can
then choose the Receive-all-files only if you want to manage OSS files.