G06.25 Release Version Update Compendium

Installation and Configuration Products
G06.25 Release Version Update Compendium529423-002
5-2
Fallback
You can add a Safeguard alias anytime that Safeguard is running and before
installing the SUT.
Before using an existing alias for DSM/SCM, verify that Safeguard is started.
Aliases are available only while Safeguard is running.
ZPHIRNM can run ZMODGP in preview mode to prediscover some errors before a
configuration is activated. However, not all errors can be displayed. Any errors in
the new and changed files might not be discovered in PREVIEW/TRIAL mode.
If you are upgrading from a pre-G06.20 RVU, besides restoring T6030D31 and
T6031D46^ABK, you must also upgrade the Software Identification (SWID)
(T9298D40^AAL or later) product at the same time to avoid a problem with
ZPHIRNM renaming hybrid SRLs to fabricated names.
Fallback
Since the introduction of G06.18, to fall back from an RVU without an installed 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, starting with G06.25, 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 reenable DSM/SCM to
manage OSS files.
If you perform a backout to your previous T6031D46 SPR after having installed
T6031D46^ABK, the FALLBACK macro removes only the Safeguard alias and
Guardian user security profile information. DSM/SCM still retains OSS management
information. New users must be reconfigured again in DSM/SCM. See the DSM/SCM
User's Guide for more information.
Note. ZMODGP makes changes to the generic-process definitions in the system
configuration database. Using ZMODGP removes the necessity to hardcode new generic-
process definitions directly into the $ZCDB (T6586, Configuration Services) process.
Note. If you fall back, you lose changes to the Guardian user IDs done before the fallback.
You also lose all Safeguard aliases.