DSM/SCM User's Guide

Troubleshooting
DSM/SCM User’s Guide — 529846-014
13 - 23
CNFGINFO Troubleshooting
CNFGINFO Troubleshooting
An Initiate Audit request
stops before it finishes.
Check any error messages appearing on the screen, and take
corrective action. You can restart the audit (press F3) or cancel
it (press F6).
The Audit function does
not seem
to be doing
anything.
The Audit function in the ZPHITI might take a long time
because SWID is run on the files for all subvolumes specified.
This fingerprinting is time consuming.
The Audit function fails
without p
roducing errors or
EMS messages.
Audit does not produce error output or EMS messages. Most
likely, the failure is caused by a file that SWID cannot
fingerprint.
Audits are performed by the COLLECT program in the SWIC
product. The file ZPHIICIN is the input
file passed to
COLLECT.
1. Check the ZPHIICIN file for which subvolumes are
being
fingerprinted.
2. Look for files on the subvolumes with security settings
such that the Pathway
owner cannot read them or for files
with old timestamps that might indicate their file formats
are a type that SWID cannot process.
COLLECT is not a DSM/SCM server and does not produce
DSM/SCM EMS messages o
r an out file when run from
DSM/SCM.
Problem Recovery
A message indicates that
no A0CINFO file is in
the
DSV.
This might indicate an old SPR or RVU that you can reobtain
from HP. You can also correct the DSV using CNFGINFO if
you know the proper attributes for the files.
If you have old SPRs or RVUs, they might not contain
A0CINFO files. Y
ou might receive an EMS message that one
or more DSVs were skipped because no A0CINFO file exists.
The input is still received if there are DSVs with A0CINFO files
in them, but the skipped DSVs must be corrected, received as
separate inputs, and used whenever you use the input they
came with originally.
The DSV location has
been entered an
d
accepted, but CNFGINFO
is not displaying the
product information
screen.
CNFGINFO can take several minutes to display the product
information screen after the DSV location is entered and
accepted because the CNFGINFO Tool server (CNFGINFO
running as $ZPHC usually) is running SWID against all files in
the DSV to get fingerprints to put in the A0CINFO file.
Problem Recovery (page 2 of 2)