DSM/SCM Messages Manual

ZPHIRNM Messages
DSM/SCM Messages Manual—529845-006
4-30
Correcting Rename Errors
Cause. ZPHIRNM cannot add a record to the from-config map file.
Effect. If a backout is performed, this file is not restored to its original name.
Recovery. If you want this file, copy it to another location.
Cause. The specified to-cnfg real file exists with the correct last modification time. But
from-cnfg and to-cnfg fabricated files do not exist.
Effect. The to-cnfg real file is used.
Recovery. Informational message; no corrective action is required.
Cause. The specified to-cnfg real-file exists with a different last modification time,
but appears to be correct. The from-cnfg and to-cnfg fabricated files do not exist.
Effect. The to-cnfg real file is used.
Recovery. Informational message; no corrective action is required.
W31 Warning: filename was an unmanaged file that was adopted
and is now managed. Received error error-number
while attempting to record this in the
from-config map file. If a backout is done, this
file will not be kept in real name. ZPHIRNM will
rename this file to fab-name .
W33 Warning: Data files indicate a rename of Real-filename
to from-cnfg fab-filename and
to-cnfg fab-filename to to-cnfg real filename is
needed. To-cnfg real-filename exists with the
correct last modification time.
From-cnfg fab-filename and
to-cnfg fab-filename do not exist.
This is unexpected but it is not a problem.
The files will be kept as they are.
W34 Warning: Data files indicate a rename of Real-filename
to from-cnfg fab-filename and
to-cnfg fab-filename
to to-cnfg real filename is needed.
To-cnfg real-filename exists with a different
last modification time,But appears to be
correct.
Expected fingerprint:
From-cnfg fab-filename and to-cnfg fab-filename
do not exist. This is unexpected but it is not a
problem. The files will be kept as they are.