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

Resolving or Accepting Discrepancies
Discrepancies are differences between the configuration of a target as it is known to NonStop
Software Essentials 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.
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.
Causes of Discrepancies
Discrepancies can occur if you:
• Apply an SPR to a product on the target system without using NonStop Software Essentials or
DSM/SCM.
• Move a TSV without using NonStop Software Essentials or 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” (page 188) .
• 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.
However, a discrepancy might result because an incorrect SPR is in the initial configuration,
and the data file is different from the one in the configuration. Even if the correct SPR is copied
to the configuration, this file is not sent to the target again until a new version of the file with
a different original fingerprint is added to the configuration.
Because a user or running software might change data files, DSM/SCM does not enforce its
normal rules about changed files. Instead, it records the original fingerprint found for the file
when the initial Build/Apply is performed. If a version of the file is later included in a
configuration revision, and its fingerprint is different from the original fingerprint in the initial
configuration, the file is considered changed.
NOTE: A fingerprint discrepancy is the only type of discrepancy that applies to OSS files.
Because TDLs cannot move, the discrepancies that apply to TSVs do not apply to OSS.
Accepting discrepancies indicates to DSM/SCM that the data files' original fingerprints are
what they should be. If discrepancies exist for data files, and a data file in the configuration
is the wrong one, DSM/SCM assumes that the data file on the target is a modified version of
the one in the initial configuration.
Create Software Audit Report
In NonStop Software Essentials, Software Audit Reports can be created to show the differences
between the currently installed files for a selected logical target and the “current” applied
configuration. This is usually the most recently applied configuration, although it will be the prior
applied configuration if the last applied configuration has been backed out. These differences
include TSV location and missing product components from the target. In other words this report
Resolving or Accepting Discrepancies 137