G06.25 Software Installation and Upgrade Guide
Overview of Installing G06.25
G06.25 Software Installation and Upgrade Guideā529430-001
1-25
C++ (G06.20)
C++ (G06.20)
The G06.20 RVU includes a fully ANSI 98-compliant C++ run-time library, designated
as the C++ v3 run-time library (v3 RTL). Starting in G06.20, you have a choice of three
different C++ language dialects: v1, v2, and v3. The default compiler dialect setting is
changed from v1 to v3. The build file for any product that invokes a TNS/R native C++
must be examined and changed according to certain rules that are documented in the
Interactive Upgrade Guide.
DSM/SCM (G06.18 through G06.25)
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, for the G06.25 RVU, 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.