DSM/SCM Messages Manual

ZPHIRNM Messages
DSM/SCM Messages Manual—529845-006
4-24
Correcting Rename Errors
Effect. Because the file is obsolete, the rename not occurring has no impact.
Recovery. Informational message; no corrective action is required.
Cause. The specified file was found in its fabricated name instead of its real name,
which was expected instead.
Effect. Because the file is present, it is used.
Recovery. Informational message; no corrective action is required.
Cause. The specified file has a different last modification time than expected, possibly
because the file changed.
Effect. This file belongs to the previous configuration only, so it does not prevent the
successful activation of the configuration.
Recovery. Informational message; no corrective action is required.
Cause. The specified unmanaged file could not be renamed because it is missing.
Effect. The file is not restored.
Recovery. None. The file does not belong to the configuration being activated.
Cause. The specified file was expected to be present in its fabricated name but is
present in its real name.
Effect. Because the file is present in real name, it is used.
Recovery. Informational message; no corrective action is necessary.
W09 Warning: Expected file filename to be in real name but
(strict) was found in fabricated name( fab-name ) instead.
This is unexpected but it is not a problem.
W10 Warning: Wrong last modification time for
real-name ( fab-name )
(strict) Actual : real-mod-time
Expected: expected-mod-time
W11 Warning: Unmanaged file, filename , could not be renamed
to real-name , because it is missing.
This file was in the way when a new file was
being put in place. ZPHIRNM was attempting to
restore the original file now that this TSV is
not part of the configuration being activated.
W12 Warning: Expected file filename to be in fabricated
(strict) name( fab-name ) but was found in real name
instead. This is unexpected but it is not a
problem. The file in real name will be used.