Using the Node Management Services (NMS) Utilities (32022-90053)

206 AppendixA
NMS Error Messages
NMFS Error and Warning Messages
ACTION: See “File System Error” at the beginning of this appendix.
MESSAGE: Datafile does not match user specified filecode.
(NMFSWARN 6)
NMFSWARN 6 CAUSE: This warning occurs when a caller of NMCONFOPEN tries to
open a file that does not have a CONF file code either because the data
file specified is not a configuration file (most likely), or because the data
file label has been corrupted in some way.
ACTION: See “Submitting an SR” at the beginning of this appendix.
MESSAGE: Unable to read root directory entry in datafile.
(NMFSERR 7)
NMFSERR 7 CAUSE: NMFILE called MIDASFILEINFO which failed on FREADDIR
after NMCONFFILEINFO was called; or MIDASFINDENTRY was
called by NMFILE, and FREADDIR failed. Most NMCONF procedures
result in a call to MIDASFINDENTRY.
ACTION: See “File System Error” and “Corrupt Configuration File” at
the beginning of this appendix.
MESSAGE: Unable to find root directory entry in datafile.
(NMFSERR 8)
NMFSERR 8 CAUSE: This error occurs when the root of the file cannot be found in
either MIDASFILEINFO or MIDASFINDENTRY. The first is called as
a result of a call to NMCONFFILEINFO. The latter is called by many
other MIDAS procedures.
ACTION: See “File System Error” and “Corrupt Configuration File” at
the beginning of this appendix.
MESSAGE: Unable to find identifier in pathname. (NMFSERR 9)
NMFSERR 9 CAUSE: This error happens when MIDASFINDENTRY cannot find an
entry with the given path name. This procedure is called internally by
several MIDAS procedures. It also results for the same reason in
MIDASRENAMEPATH (from a call to NMCONFRENAMEPATH) and
MIDASPURGEPATH (from a call to NMCONFPURGEPATH). This is a
user error. Make sure the pathname requested was previously entered
into the file.
ACTION: Check spelling.
CAUSE: This error happens when MIDASFINDENTRY cannot find an
entry with the given path name. This procedure is called internally by
several MIDAS procedures. It also results for the same reason in
MIDASRENAMEPATH (from a call to NMCONFRENAMEPATH) and
MIDASPURGEPATH (from a call to NMCONFPURGEPATH). The file
might be corrupt
ACTION: See “Corrupt Configuration File” at the beginning of this
appendix