beautypg.com

Proceed to, Task 8: accepting discrepancies – HP Integrity NonStop H-Series User Manual

Page 122

background image

Configuring DSM/SCM

DSM/SCM User’s Guide — 529846-014

5 - 37

Reinitializing DSM/SCM

HP recommends that you perform an initialization Build/Apply before you perform
the full Build/Apply. A full Build/Apply builds a new SYSnn and places the new
software in the TSVs.

Task 7: Activate the New Software on the Target System

After the software is placed in the appropriate TSVs, you need to activate the new
software. Run ZPHIRNM to rename the old software files to fabricated names while the
new software is renamed to the appropriate real name. See

Section 10, Activating New

Software on a Target System

.

Task 8: Accepting Discrepancies

Discrepancies are differences between the configuration of a target as it is known to
DSM/SCM and the actual configuration on that target. After an Initialization Build/Apply,
you must accept any discrepancies. Resolving discrepancies that arise minimizes the
chances that they will affect your system. You can resolve discrepancies at any time
after applying an initialization package to a target.

Causes of Discrepancies

Discrepancies can occur if you:

Apply an SPR to a product on the target system outside DSM/SCM.

Move a TSV outside DSM/SCM.

Duplicate TSVs. If you find duplicate TSVs, you need to perform a new Build/Apply.
To avoid duplicate TSVs, identify TSV locations correctly at the time of the
initialization Build/Apply. See

Discrepancy Troubleshooting

on page 13-17.

Move or delete files.

Change data files. Discrepancies are often caused by data files (such as edit files
and structured files) that changed in the course of normal operation.

For example, a data file discrepancy can occur if an SPR is on the target system
but was not included in the initial configuration revision. As a result, this data file is
not sent to the target system until a new version of the file containing a different
original fingerprint is included in a configuration revision. The discrepancy is not a
problem if the data file on the target is the correct one, and it has just been
changed on the system.

Note. You are not required to resolve discrepancies to continue. You only need to be aware of
the differences and understand what they mean when the next configuration is applied. You
must accept the discrepancies before you can proceed.

This manual is related to the following products: