DSM/SCM User's Guide
Backing Out a Revision
DSM/SCM User’s Guide — 529846-014
15 - 8
After Renaming the SYSnn
2. Run ZPHIRNM on the previous SYSnn (in this example, SYS20). For more
information, refer to Run ZPHIRNM on page 11-4. The previous SYSnn is the
software configuration that was running before the current software configuration.
3. Rename the current SYSnn (SYS00) and CSSnn (CSS00) to an unused SYSnn
(SYS01) and CSSnn (CSS01), respectively. For example:
> FUP RENAME $SYSTEM.SYS00.*, $SYSTEM.SYS01.*
> FUP RENAME $SYSTEM.CSS00.*, $SYSTEM.CSS01.*
4. Rename the previous SYSnn 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 SYSnn (SYS00), which now contains the
revision before the last update.
6. Restart DSM/SCM.
7. Update the DSM/SCM database with the new SYSnn subvolumes. (You do not
need to do this immediately, but do it as soon as possible in case you need to back
out to the previous revision.)
a. Before the next Apply to the system, run a Verify Database so that DSM/SCM
can resolve the current names of the SYSnn subvolumes.
b. Create an independent snapshot of the target.
c. Receive the independent snapshot into the host database.
System Load Fails or DSM/SCM Does Not Run Correctly
1. Perform a system load from the previously working SYSnn (renamed to SYS20).
2. Rename the current SYSnn (SYS00) and CSSnn (CSS00) back to the last built
SYSnn (SYS01) and CSSnn (CSS01), respectively. For example:
> FUP RENAME $SYSTEM.SYS00.*, $SYSTEM.SYS01.*
> FUP RENAME $SYSTEM.CSS00.*, $SYSTEM.CSS01.*
3. Rename the previous SYSnn
to the name it had at the completion of the Apply. For
example:
> FUP
> RENAME $SYSTEM.SYS20.*, $SYSTEM.SYS00.*
> RENAME $SYSTEM.CSS20.*, $SYSTEM.CSS00.*
4. Run ZPHIRNM to reverse the ZPHIRNM done before the SYSnn subvolume was
renamed. For more informa
tion, refer to
Run ZPHIRNM on page 11-4. For
example:
> RUN ZPHIRNM $volume.SYS00, FROM $volume.SYS01