G06.25 Software Installation and Upgrade Guide

Overview of Installing G06.25
G06.25 Software Installation and Upgrade Guide—529430-001
1-20
Using DSM/SCM FALLBACK and CLEANOSS
Macros
Using DSM/SCM FALLBACK and CLEANOSS Macros
Since the introduction of G06.18, if you had to fall back from an RVU that did not have
installed the D46 DSM/SCM PVU, you had to run the DSM/SCM FALLBACK macro
from the ZDSMSCM subvolume. If a D46 PVU existed, you did not have to run the
FALLBACK macro. However, you must run the FALLBACK macro whether or not you
have installed a T6031D46 SPR. The interactive macro must be run by the DSM/SCM
owner or by super ID (255,255). The FALLBACK macro reverts the DSM/SCM Host or
Target, or both, database back to a pre-T6031D46^ABK state.
If you perform a backout to a pre-D46 version after having installed T6031D46^ABK or
later, the FALLBACK macro removes both OSS management information and the
Safeguard alias and Guardian user security profile information. You must still use the
COPYOSS procedures to install OSS software until you re-enable DSM/SCM to
manage OSS files.
If you perform a backout to your previous T6031D46 SPR after having installed
T6031D46^ABK, the FALLBACK macro only removes the Safeguard alias and
Guardian user security profile information. DSM/SCM still retains OSS management
information. New users must be re-configured again in DSM/SCM. See the DSM/SCM
Users’ Manual for more information.
If a Host and Target system are running on the D46 product version of DSM/SCM and
only the Host falls back to a pre-D46 PVU or pre-ABK SPR, run the FALLBACK macro
only on the Host system.
Notes on the FALLBACK Macro
Retrieve the FALLBACK macro from the SUT before falling back or use the FUP DUP
command to copy it to a subvolume for use during fallback.
Note that you can migrate back to an earlier RVU SUT version without migrating back
to an earlier DSM/SCM version. To do this and eliminate the need to run the
FALLBACK macro, copy T6031D46 into the configuration on top of the older SUT. See
the DSM/SCM User’s Guide for more information.
Notes on the CLEANOSS Macro
If you fall back and then migrate to a G06.18 or later RVU, DSM/SCM might notify you
during the Apply that the CLEANOSS macro must be run. The current OSS
environment is being managed by a logical target other than the one trying to manage
OSS files with the current DSM/SCM Build/Apply. You must cancel the Apply, and run
the CLEANOSS macro. The EMS message gives you basic instructions:
The current OSS environment is managed by target oss-system
(according to /zzDSMSCM.Managed). To switch OSS management
from oss-system to target-system, CANCEL the Apply, run
CLEANOSS, run Verify Database, then RESTART the Apply.