DSM/SCM User's Guide

Managing DSM/SCM
DSM/SCM User’s Guide — 529846-014
17 - 19
Creating an Independent Snapshot of the Target
System
When the Verify Database request finishes successfully, DSM/SCM displays an
informational message.
Creating an Independent Snapshot of the Target System
A snapshot of a target system provides current target database information to transfer
to the host system and receive into the host database. With current information about
the target contents, DSM/SCM can keep the host and target databases synchronized,
which is crucial to effective system configuration management. You should create a
snapshot after most DSM/SCM tasks on a target. A snapshot includes:

The physical target name

The SYSnn and configuration name of each logical target on the target system

The TSV locations associated with each logical target

File attributes, including fingerprints of each managed file on the target system

Activity records from the target system

The target’s EMS messages

Target system profile information

Disk and tape device locations on the target system

Name and timestamp of when the snapshot was generated
If you submit a Build/Apply request, a snapshot is automatically created, transferred to
the host system, and received into the host database. The planner might request an
independent snap
shot for one of these reasons:

Software on the target system has changed outside of a Build/Apply.

The host snapshot is lost or corrupted.
Note. If $DATA00 is a scratch volume, Verify Database stops in restartable mode giving
an EMS message that no scratch volumes are configured on the target system.
Define at least one scratch volume using the Target Maintenance and restart the Verify
Database activity.
Af
ter successful completion of Verify Database, update the volume usage information
using the ZPHIHMI also.
If $
DATA00 is an archive volume, after successful comple
tion of V
erify Database, update
the volume usage information using the ZPHITMI and ZPHIHMI.
For more information, see
Updating the Volume Usage on page 17-11.
Note. When it receives a snapshot from a target system, DSM/SCM creates a configuration
report that list
s each logical target, its products, and SPRs applied to the products on the
target. DSM/SCM then notifies the OSM application, which in turn creates a Software
Configuration Incident report and delivers it to the GCSC.