DSM/SCM User's Guide
Generating DSM/SCM Reports
DSM/SCM User’s Guide — 529846-014
18 - 3
Standard Reports
Configuration 
Product Files
Provides a detailed picture of the contents 
of a configuration by product, shows the 
TSV locations of all product files in the 
configuration, and gives the software input 
name for each product component file.
The specified configuration name, product 
name, product number
, product version, 
base SPR number, and update SPR 
number appear at the head of each group 
of product version files.
If the logical target for the specified 
configur
ation manages OSS files, this 
report contains a second section showing 
each OSS files’ pax file, file type, and fully 
qualified OSS filename.
Use to determine what 
software versions ex
ist on a 
system when you are planning 
an update.
Configuration 
Products
List
s the current set of products for a 
selected target.
Use to determine if a target 
contains the expected set of 
products.
Contents of 
All Configs
For all t
arget systems managed by a 
particular host, lists each system’s logical 
targets, the products on each target, and 
the SPRs applied to those products.
Use to determine what 
software versions exist on 
many systems when you are 
planning an update. If you 
have several similarly 
configured systems, this saves 
you from creating several 
individual configuration reports.
Discrepancy Lists the differences between the latest 
snapshot
 for a specified target system and 
the most recently applied configuration on 
that system. Compares files expected to 
be placed on a logical target to the files 
actually on that logical target.
If the specified configuration manages 
OSS files, a second section of th
is report 
shows fingerprint discrepancies for OSS 
files. (Unlike TSVs in Guardian, TDLs 
cannot move, so they are not listed.)
Use when adding a new 
system 
to DSM/SCM. See 
Task 8: Accepting 
Discrepancies on page 5-37. 
Table 18-1.  Standard DSM/SCM Reports  (page 2 of 5)
Report name Contents Usage










