Using the Node Management Services (NMS) Utilities (MPE/iX 7.0, 7.5)

Appendix A 215
NMS Error Messages
NMFS Error and Warning Messages
NMFSERR 10 MESSAGE: Directory linkage error in datafile. (NMFSERR 10)
CAUSE: This error occurs when there is a failure in an FREADDIR in
the MIDAS procedures shown in the table when the next link or the
root cannot be found. Specifically, an unexpected end of file was found.
ACTION: See “Corrupt Configuration File” at the beginning of this
appendix.
NMFSERR 11 MESSAGE: Unable to read directory entry in datafile. (NMFSERR 11)
CAUSE: This error is similar to message NMFSERR 10 except that the
end of file was not the error when FREADDIR was called.
ACTION: See “File System Error” and “Corrupt Configuration File” at
the beginning of this appendix.
NMFSERR 12 MESSAGE: Data is already associated with this identifier.
(NMFSERR 12)
CAUSE: This error is returned by MIDASADDDATA when data already
exists at the location where it was to be added.
ACTION: See “Corrupt Configuration File,” “Invalid Software
Installation,” and “Submitting a CR” at the beginning of this appendix.
NMFSERR 13 MESSAGE: Unable to retrieve freespace pointer from datafile.
(NMFSERR 13)
CAUSE: This error is returned by the MIDAS procedures listed in the
table when there is an FGETINFO to find the last record and there is a
failure of that call.
ACTION: See “File System Error” and “Corrupt Configuration” at the
beginning of this appendix.
NMFSERR 14 MESSAGE: Filespace exhausted. Unable to add entry. (NMFSERR 14)
CAUSE: This is caused when FGETINFO returns insufficient file space
left for an additional entry in the configuration file.
ACTION: Compress configuration file. If this does not resolve the error,
add records to the configuration file.
NMFSERR 15 MESSAGE: Unable to write data record to datafile. (NMFSERR 15)
CAUSE: This is due to an FWRITEDIR failure.
ACTION: See “File System Error” and “Submitting a CR” at the
beginning of this appendix.
NMFSERR 16 MESSAGE: Unable to write directory entry to datafile. (NMFSERR 16)
CAUSE: This is due to an FWRITEDIR failure.
ACTION: See “File System Error” at the beginning of this appendix.