DSM/SCM User's Guide

Troubleshooting
DSM/SCM User’s Guide — 529846-014
13 - 21
Maintenance Interface Troubleshooting
Maintenance Interface Troubleshooting
Problem Recovery
The New Revision Window
or Build/A
pply dialog box
does not appear.
The New Revision window can take a while to appear as the
data on the configuration is retrieved and sent to the PC.
The Build dialog box also takes several minutes to appear
because many ac
tivities are going on to get the information
that is displayed to the user:
1. SWID is run on CONFTEXT to see if changes imply that a
system generation must b
e done.
2. The previous snapshot and the current revision are
compared to dete
rmine what files have changed in the
new revision.
3. Based on file changes since the last snapshot, DSM/SCM
determines whether it need
s to run system generation,
OSM (because of firmware changes), SCF (because of
bootstrap changes), or INSTALL^TEMPLATES for EMS
templates or SCF for IOP changes (if system generation
was not required).
4. The TSV locations for the configuration are determined
and returned to th
e Planner Interface, along with other
miscellaneous information.
Problem Recovery (page 1 of 2)
ZPHIHMI or ZPHITMI
logons do no
t seem to
be
doing anything.
If MISERVER is not running, and if a database manager needs
to be started, the logons might seem to take a long time while
the database manager process starts. The KBD LOCK
indicator appears on the requestor screen while this occurs.
Also, the ZPHIHMI functions of archive and database
maintenance take long periods of time during which the
requestor displays KBD LOCK.
The Relocate Database
function doe
s not seem to
be doing anything.
The database relocate function might also take several
minutes because the database manager for the catalog must
also be copied to the new location and SQLCOMP must be run
there.
The Archive Maintenance
and Delete System d
oes
not seem to be doing
anything.
Because files are only put in the archive once even if they exist
in multiple software inputs, deleting or backing up software in
the archive must update many database entries. Files in the
input being backed up or deleted remain on the system if they
are also referenced by another software input.
A Database Relocate fails
with an internal error 507.
A TMF error o
r a SQL/MP error occurred during the operation.
For more information on the error, view the DBRELOUT file in
the ZDSMSCM subvolume.