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

ASSIGNs and PARAMs
DSM/SCM User’s Guide — 529846-014
E - 16
OVERRIDE-SYSNN and OVERRIDE-SYSNN-
DIFFERENT-OS Params

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.

Check the CONFLIST and CONFAUX files. The new one is replaced, and the old
one is renamed to a fabricated name. Only the timestamps should be different.

Check the CONFTEXT file. If it changed, the new one is replaced, and the old one
is renamed to a fabricated name. Only the timestamps should be different.

Run ZPHIRNM in preview mode to check the files to be renamed. No files critical
to running the SYSnn should be renamed.
Checking the OSIMAGE File After INITENV
To verify that the new and running OSIMAGEs are the same after an INITENV:
1. FUP DUP the latest SYSHnnnn file to a temporary subvolume. For example:
FUP DUP $DSMSCM.ZDSMSCM.SYSH0001, temp. SYSH0001, saveall
2. Run INITENV.
3. Set up DSM/SCM (profiles, receive software, and so on).
4. Perform an Initialization Build/Apply. SYSGEN is not performed for an Initialization
Build/Apply.
5. Run a Discrepancy Report and check for differences. Only the SRL files should be
different.
6. On the next Build/Apply, system generation is automatic. Use the statement:
PATHCOM $YPHI;ALTER ta-001,PARAM override-sysnn
logical^targetrevision
For example:
PATHCOM $YPHI;ALTER ta-001,PARAM override-sysnn default2
7. Use QACOMP to compare the old SYSHnnnn file with the new one from this
Build/Apply:
QACOMP TEMP.SYSH0001,ZDSMSCM.SYSH0001
Only three lines should be different:

Date of the report

The configuration revision number

The apply date line