HP Integrity NonStop H-Series - Manual (Page 279)

Backing Out a Revision
DSM/SCM User’s Guide — 529846-014
15 - 10
Removing OSS Management Information From the
DSM/SCM Databases

You performed a backward migration from T6031ABK or later to pre-D46. In this
case, in addition to the new security tables, FALLBACK also removes OSS
management information from the DSM/SCM databases. (For details, see
Removing OSS Management Information From the DSM/SCM Databases .)
The FALLBACK macro is run in the same manner as explained on page 12-2.
Removing OSS Management Information From the DSM/SCM
Databases
Backing out to the previous configuration is the same when OSS files are managed as
when only Guardian files are managed, with one exception: the current configuration
manages OSS files, but the previous configuration did not.
The backout and activation processes are normal, and OSS files are returned to the
state they were in before the current configuration was applied. However, this backout
puts DSM/SCM in a unique state where the newly current configuration does not
manage OSS files but the newly previous configuration does. There are three possible
results:

If the next Build/Apply is for this logical target and does not manage OSS files,
OSS management is removed.

If the next Build/Apply is for this logical target and manages OSS files, the build
stops restartable:
1. Cancel the Apply.
2. Run CLEANOSS to remove all DSM/SCM files from the OSS environment.
3. Run Verify Database to remove OSS management from the logical target in the
target database.
4. Restart the Apply.

If you back out from a configuration managed by a D46 or later DSM/SCM PVU to
one managed by a pre-D46 PVU, you must revert your DSM/SCM host and target
databases to their pre-OSS management setup.
To revert the databases for use by pre-D46 DSM/SCM PVUs, use the FALLBACK
macro:
1. Find the FALLBACK macro.
The macro was first released with T6031D46 in the ZDSMSCM subvolume. If you
have already reverted to a pre-D46 DSM/SCM PVU, it is likely not in the
ZDSMSCM subvolume. You can retrieve the macro from the T6031D46 DSV in
any G06.18 or later RVU. If such an RVU is in the DSM/SCM archive, you can
export it directly from the archive.
2. Check that DSM/SCM is stopped.