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

3. Pass KEEP-OBSOLETE-SYSNN to the TA:
•
Subsequent obsolete SYSnn subvolumes and CSSnn subvolumes, such as SYS00 and
CSS00 in Step 2, are saved and become unmanaged.
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
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” (page 247) . 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.
Results PARAMs Used Configuration Need
Overriding is not allowed. None Normal update, system load is
acceptable
Overriding is not allowed. OVERRIDE-SYSNN-DIFFERENT-OS (Never use this PARAM by itself)
If the new and target OSIMAGE EOFs
are the same, overriding is allowed.
Otherwise, overriding is not allowed. OVERRIDE-SYSNN You can create the same configuration,
system load not acceptable
Overriding is allowed. OVERRIDE-SYSNN and
OVERRIDE-SYSNN-DIFFERENT-OS You cannot create the same
configuration, system load not
acceptable
Using OVERRIDE-SYSNN
To avoid a system load, insert these steps in your Build/Apply process:
1. Check that the configuration is unchanged.
2. Check that the host system is running DSM/SCM T6031AAX or later.
3. In PATHCOM, specify the OVERRIDE PARAM:
PATHCOM $YPHI
=Alter TA-001, PARAM OVERRIDE-SYSNN &
"logical_targetRevision"
4. Start the Build/Apply in DSM/SCM.
5. When the Apply starts, watch the messages.
DSM/SCM checks for OVERRIDE PARAMs and matches their values with the applied
configuration revision. If there is a match, the Apply continues to the target SYSnn without
246 ASSIGNs and PARAMs