G06.30 Software Installation and Upgrade Guide

Preparing to Fall Back
G06.30 Software Installation and Upgrade Guide—543764-002
13-4
DSM/SCM
See the appropriate programming documentation for details on C++ and compilers. For
a list of participating products, see the Interactive Upgrade Guide 2.
DSM/SCM
You must run the FALLBACK macro before starting DSM/SCM unless you are
currently on T6031D46^ABK. See DSM/SCM on page 1-28.
If you fall back to a pre-D46 product version 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. You must cancel the Apply, and then run the CLEANOSS macro. For detailed
information on the FALLBACK and CLEANOSS macros, see the DSM/SCM User’s
Guide and Notes on the CLEANOSS Macro on page 1-24.
The G02 DSM/SCM client software is backwards compatible with most DSM/SCM
server versions.
Spooler
If your previous product version of spooler was T9101D41 SPR ADM or later, you do
not need to restore copies of both the control file and the collector data files if you back
out of your G06.30 RVU. All versions of T9101D41, starting with T9101D41^ADM,
contain Version 5 of the spooler control file and are compatible with T9101D46 and
D48 product versions of spooler. However, it is always recommended that you back up
the spooler control file and collector data files before migrating or applying spooler
SPRs.
See Support Notes S97057 (T9101D41 Spooler Collector Data Files Have Changed
Format) and S99086 (NSK Spooler — Migration and Draining Instructions) for more
information.
OSS
Back up the OSS configuration database files before falling back. See the Open
System Services Management and Operations Guide for more information.
OSM and TSM
See the OSM Migration and Configuration Guide for complete information. If you
installed OSM after installing the G06.30 RVU and you want to fall back to a newer
SPR of TSM, see TSM Server and Client Compatibility SPRs on page 3-12 and the
Interactive Upgrade Guide 2. Information on uninstalling OSM is presented in the OSM
Migration and Configuration Guide.