Example 5-1, Discrepancy report, Example 5-1. discrepancy report – HP Integrity NonStop H-Series User Manual
Page 123
![background image](/manuals/397210/123/background.png)
Configuring DSM/SCM
DSM/SCM User’s Guide — 529846-014
5 - 38
Reinitializing DSM/SCM
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.
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.
Discrepancy Report
A discrepancy report is a standard DSM/SCM report that details any differences
between what a snapshot indicates is on a specified target system and what is actually
in the configuration most recently applied to the target. To help you isolate data file
discrepancies, the discrepancy report lists discrepancies for nondata files in a product
followed by discrepancies for all of its data files. If you use DSM/SCM to manage OSS
files, OSS discrepancies are listed in a separate section after Guardian file
discrepancies.
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.
Example 5-1. Discrepancy Report
Expected TSV Location: Expected TSV ~ File Name ~ Actual TSV Location Actual TSV
---------------------- ------------ ~ --------- ~ ------------------- ----------
Product Name:DUPLICATE TSV INFO
Product Number:
Product Version:
$SYSTEM ZTMF ~ ~ $ARCHIVE ZTMF
$SYSTEM ZTMF ~ ~ $DATA ZTMF
$SYSTEM ZTMF ~ ~ $SYSTEM ZTMF
Product Name:DSM/SCM - TARGET COM
Product Number:T6031
Product Version:D46
$SYSTEM ZDSMSCM ~ HELPSRVO ~ $DATA ZDSMSCM
$SYSTEM ZDSMSCM ~ OSECUREL ~ $DATA ZDSMSCM
BEGIN DATA ~ FILES
$SYSTEM ZDSMSCM ~ INITENV ~ $DATA ZDSMSCM
$SYSTEM ZDSMSCM ~ VERIFYI ~ $DATA ZDSMSCM