DSM/SCM User's Guide

Troubleshooting
DSM/SCM User’s Guide — 529846-014
13 - 14
Build/Apply Troubleshooting
You might get error 5025 during an
Apply if:
Any time a Build completes
successfully, system generation was
unnecessarily performed:
Modifying comments in the
CONFTEXT file forces system
generation. When the fingerprint of the
CONFTEXT file indicates that the file
changed but the system generation
instructions in the file did not change.
For example: Configuration DEFAULT
7 was applied to SYS00. A new
configuration DEFAULT 8 that
requires system generation is built.
Once the DEFAULT 8 Build completes
successfully, you cannot use SYS00.
That is, if you create DEFAULT 9
identical to DEFAULT 7, system
generation is required, and you cannot
send the configuration to SYS00,
regardless of whether DEFAULT 8
was applied, or applied and backed
out.
INITENV. When you reinitialize,
DSM/SCM does not let you send your
first real Apply to the current SYSnn,
even when the OSIMAGE files are
identical. INITENV equates to a
system load.
See the DSM/SCM Messages Manual.
A configuration revision still shows
Pending for the application date even
though the snapshot for the
Build/Apply has already been
received.
When the snapshot for a
Build/Apply is
received, the Planner Interface screens
might not be automatically updated. Select
Window>Refresh before the date that the
Apply occurred (Application Date) is
updated and before the next Build/Apply for
that target is initiated.