DSM/SCM Messages Manual

ZPHIRNM Messages
DSM/SCM Messages Manual—529845-006
4-28
Correcting Rename Errors
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 must be renamed to make room for a new file,
but the unmanaged file’s new fabricated name could not be recorded in the map file
due to the specified error.
Effect. If a backout is performed, ZPHIRNM might not be able to rename this file to its
real name.
Recovery. Informational message; no corrective action is required. The file is purged
when it is no longer needed.
Cause. ZPHIRNM cannot rename a file because an unmanaged file is in the way.
Effect. The unmanaged file is not restored.
Recovery. If you want this file, rename the copy to another location.
W24 Warning: Wrong last modification time for
real-name ( fab-name )
(strict) Actual : real-mod-time
Expected: expected-mod-time
W25 Warning: filename is an unmanaged file that is in the way
and will be renamed to fab-name . Received error
error-number while attempting to record this in
the from-config map file. If a backout is done,
ZPHIRNM may not be able to rename this file back
into place.
W26 Warning: Unmanaged file, filename , could not be renamed
to fab-name , because another unmanaged file is
in the way. 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.