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

ASSIGNs and PARAMs
DSM/SCM User’s Guide — 529846-014
E - 14
OVERRIDE-SYSNN and OVERRIDE-SYSNN-
DIFFERENT-OS Params
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 replacing the OSIMAGE. No system load is required because the
system continues running on the same OSIMAGE.
Using the OVERRIDE-SYSNN-DIFFERENT-OS Param
If error 5023 or 5028 appears and stops the Apply in a restartable state:
1. Use the OVERRIDE-SYSNN-DIFFERENT-OS PARAM:
> PATHCOM $YPHI

= Alter TA-001, PARAM OVERRIDE-SYSNN-DIFFERENT-OS &
"logical_targetRevision"
2. In the Target Interface, restart the Apply request.
3. When the Apply finishes, run ZPHIRNM in preview mode. Check that no files
critical to the execution of the current SYSnn are being renamed.
Configuration Need Params Used Results
Normal update, system load
is acceptable None Overriding is not allowed.
(Never use this PARAM by
itself) OVERRIDE-SYSNN-
DIFFERENT-OS Overriding is not allowed.
You can create the same
configuration, system load
not acceptable OVERRIDE-SYSNN If the new and target OSIMAGE
EOFs are the same, overriding
is allowed. Otherwise, overriding
is not allowed.
You cannot create the same
configuration, system load
not acceptable OVERRIDE-SYSNN and

OVERRIDE-SYSNN-
DIFFERENT-OS
Overriding is allowed.