DSM/SCM Messages Manual
ZPHIRNM Messages
DSM/SCM Messages Manual—529845-006
4-27
Correcting Rename Errors
Cause. ZPHIRNM found that the specified files already exist in their real names, which
was not expected.
Effect. Because the files are already present in their real names, they are used.
Recovery. Informational message; no corrective action is required.
Cause. An error occurred when ZPHIRNM tried to get information for the indicated file.
Effect. The last modification time is not verified.
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 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.
W20 Warning: Data files indicate a rename of
fab-name
(strict) to
real-name
, and
fab-name
to
real-name
is
needed. It appears that these renames have
already been done because
real-name
and
real-name
exist, but
fab-name
does not exist.
This is unexpected but it is not a problem. The
files will be kept as they are.
W21 Warning: FILEINFO error on file
filename
Unable to verify LMT on file. Continuing.
Data files indicate that a rename of
fab-name
to
real-name
is needed, but both files exist.
This is unexpected but it is not a problem. The
existing file
filename
will be used.
W22 Warning: Wrong last modification time for
filename
(strict) Actual :
real-mod-time
Expected:
expected-mod-time
W23 Warning: Wrong last modification time for
filename
(strict) Actual :
real-mod-time
Expected:
expected-mod-time