DSM/SCM User's Guide

Generating DSM/SCM Reports
DSM/SCM User’s Guide — 529846-014
18 - 13
Creating a System Report
To create a custom report:
1. Create a new IN_file, or make a copy of an existing DSM/SCM IN_file in the SQL
catalog subvolume to use as a template.
If you do the latter, work from a copy of the IN_file. Do not modify the original
IN_file.
2. Use a text editor to change the file. You can modify commands, syntax elements,
and database fields to customize the information to include in the report:

To extract values from the database to include in the report, add a SELECT
statement.

Modify the default format to any format you want.

Define parameters to use as input to the report.
3. Store the IN_file in the SQL catalog subvolume.
4. Add the report to DSM/SCM. (See Adding and Deleting Reports on page 18-15.)
Creating a System Report
A system report gives the planner a complete high-level picture of what software is on
each target system and where the software is located. System reports are created at
the request of a planner or as part of normal procedures for controlling changes to
software revisions on a target system.The system report contains a list of:

All logical targets on the target system.

All software managed by DSM/SCM on a particular target system at a given time,
including:

The name and location of every DSM/SCM-managed TSV (and TDL, if the
specified logical target manages OSS files) in each configuration on the target
system

The name and fingerprint of the files on each DSM/SCM-managed target
subvolume
To create a system report:
1. At the ZPHITI main menu, enter 1 (Create system report) in the Selection number
field, and press F1.
DSM/SCM displays the System Report screen.
2. Specify the output location for the report:
Note. Parameters in reports are case-sensitive. For example, a SELECT for \system is
not the same as a SELECT for \SYSTEM. The parameter description provided with each
report gives examples for all parameters. However, because reports are customizable,
DSM/SCM does not try to determine the proper case for a parameter.