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

replacing the OSIMAGE. No system load is required because the system continues running
on the same OSIMAGE.
Using OVERRIDE-SYSNN-DIFFERENT-OS
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.
Considerations
• After using the OVERRIDE-SYSNN PARAM once, you must specify the PARAM for every Apply
until you perform a system load.
• A Discrepancy Report still shows the OSIMAGE on the system is different from that in the
configuration. However, a Verify Database does not detect a difference.
• The Apply takes longer with OVERRIDE-SYSNN because:
—
All files manufactured by the system generation program in the executing SYSnn are
fingerprinted to compare against the same files in the new configuration.
— Adoption extends to adopt any files in the executing SYSnn with the correct fingerprint
but not the correct EOF and LMT. Files not adopted because of matching EOF and LMT
are fingerprinted.
This is necessary when applying to an executing unmanaged SYSnn. Otherwise, no SRL
files, among others, would be adopted (which means they are replaced). The LMT of SRL
files in a new configuration never matches the LMT of SRLs on the target system because
SRLs are rebuilt on every Build.
• When you enter the Build/Apply request, NonStop Software Essentials might indicate that
system generation or system load is required because the EOF of OSIMAGE can be compared
only after the Build finishes.
• All subsequent Build/Apply requests, until you send one to a new SYSnn, report that a system
load is required. The fingerprint of the last OSIMAGE built for this configuration does not
match the OSIMAGE fingerprint last applied. If you are using the OVERRIDE feature, you can
ignore the message that indicates a system load is required.
Checking the OSIMAGE File
Checking That the OSIMAGE File is Unchanged
To check that your OSIMAGE file is unchanged:
• If you did not run INITENV:
—
Run the Configuration Differences report to compare the configuration last applied to the
SYSnn against the new configuration.
— Run a discrepancy report between the files on the target system and the new configuration.
Discrepancy reports do not compare files manufactured by a system generation program.
• If you ran INITENV, perform an Initialization Build/Apply to verify that the files on the system
match the files in your new configuration. The discrepancy report does not compare
SYSGEN-manufactured files.
• Check that the OSIMAGE EOF is the same. Otherwise, OVERRIDE-SYSNN-DIFFERENT-OS is
required.
• Compare the old and new configuration dial-out reports (SYSHnnnn files in ZDSMSCM). This
report contains all products and their versions in the configuration. To Apply to the executing
SYSnn after initializing DSM/SCM, capture the old configuration report before initializing.
Specifying a PARAM from PATHCOM 247