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

ASSIGNs and PARAMs
DSM/SCM User’s Guide — 529846-014
E - 13
OVERRIDE-SYSNN and OVERRIDE-SYSNN-
DIFFERENT-OS Params
4. Build/Apply and system load SYS03:

SYS01 and CSS01 become obsolete and unmanaged but are not purged.

SYS02 becomes the previous configuration.
5. Delete the KEEP-OBSOLETE-SYSNN PARAM.
6. Build/Apply and system load SYS04:

SYS02 and CSS02 are purged.

SYS01 and CSS01 are not purged by DSM/SCM, but you can purge them
manually at any time.
OVERRIDE-SYSNN and OVERRIDE-SYSNN-DIFFERENT-OS
Params
You can force an Apply to the current SYSnn subvolume. DSM/SCM ignores the new
OSIMAGE, avoiding a system load and preventing downtime.
See Checking That the OSIMAGE File is Unchanged on page E-15. You cannot use
OVERRIDE-SYSNN if:

The configuration really changed and it requires a new OSIMAGE for the target
SYSnn.

DSM/SCM can perform the Apply to the target SYSnn without the OVERRIDE
PARAMs. In that case, system generation is not needed for the new configuration
and the new OSIMAGE is the same as the one already in the target SYSnn.

The target SYSnn is a nonexecuting current configuration SYSnn. subvolume
If you cannot construct the same configuration but believe critical files are not affected
by the update, you can use the OVERRIDE-SYSNN and OVERRIDE-SYSNN-
DIFFERENT-OS PARAMs.
Caution. Use the OVERRIDE-SYSNN-DIFFERENT-OS PARAM with caution. Problems can
arise if critical files are affected.