DSM/SCM User's Guide

Building and Applying a New Configuration
DSM/SCM User’s Guide — 529846-014
9 - 2
Build Types
Build Types

Normal Build/Apply on page 9-2

Initialization Build/Apply on page 9-2

FRABIBAB on page 9-3
Normal Build/Apply
In most cases, you perform a normal build and apply. This is required to migrate to a
new RVU.
Initialization Build/Apply
When you initiate the Build/Apply from the Initialize target system dialog box,
DSM/SCM displays the Indicate Type of Build window instead of the Build/Apply
Request window.
Full Activation Package
DSM/SCM applies all the software in the activation package on the system regardless
of what is already there. A normal Build/Apply applies only files that are different from
the existing software configuration. Consequently, a full activation package is large and
takes a long time to configure.
However, if the full activation package contains a configuration similar to the existing
configuration on the target, the time might be greatly reduced by file adoption. Any
existing files that match new files are adopted, rather than reinstalled, reducing
installation time.
Existing files that are not adopted are renamed and available only if you back out.
DSM/SCM manages only the files in this full activation package. It does not manage
any existing files that were not adopted. Also, if the new and existing configurations are
not similar, check that enough disk space is available on the system to place what is
effectively a second complete software configuration on your system.
Initialization Package
You cannot migrate to a new RVU using an initialization package.
An initialization package synchronizes the host database with what is actually on a
ta
rget system. DSM/SCM compares the currently existing software on the system with
the software configuration you created. It does not modify the software configuration
on the target system. No activation package files are applied to the target system.
A discrepancy report shows the differences between the currently running software
and the software just configured. Evaluate the report and determine which
discrepancies are acceptable and which need to be resolved. After you are satisfied
that the discrepancies will not cause operational problems, you can perform a full