DSM/SCM Quick Reference Guide

Backing Out a Revision
DSM/SCM Quick Reference Guide—529847-005
4-8
If the System Load and DSM/SCM Restart Succeed
2. Run ZPHIRNM on the previous SYS nn (in this example, SYS20). The previous
SYS nn is the configuration that was running before the current configuration.
3. Rename the current SYS nn (SYS00) and CSS nn (CSS00) to an unused SYS nn
(SYS01) and CSS nn (CSS01), respectively. For example:
> FUP RENAME $SYSTEM.SYS00.*, $SYSTEM.SYS01.*
> FUP RENAME $SYSTEM.CSS00.*, $SYSTEM.CSS01.*
4. Rename the previous SYS nn to the name it had at the completion of the Apply.
For example:
> FUP
> RENAME $SYSTEM.SYS20.*, $SYSTEM.SYS00.*
> RENAME $SYSTEM.CSS20.*, $SYSTEM.CSS00.*
5. Perform a system load on your usual SYS nn (SYS00), which now contains the
revision before the last update.
6. Restart DSM/SCM.
7. Update the DSM/SCM database with the new SYS nn s:
a. Before the next Apply to the system, run Verify Database so that DSM/SCM
can resolve the current names of the SYS nn s.
b. Create an independent snapshot of the target.
c. Receive the independent snapshot into the host database.