NMFS Error and Warning Messages

Table-Bottom ↓

MESSAGE: Unable to create new datafile. (NMFSERR 1)

Level: NMFSERR 1 CAUSE: This error occurs when NMFILE cannot create a new file that is requested by a call to NMCONFOPEN, because of an error in an FOPEN. It could be due to a faulty call to NMCONFOPEN or an error due to specific problems on the system itself, such as insufficient disk space or an I/O error on the file label. ACTION: See "File System Error" and "Submitting a CR" at the beginning of this appendix.

MESSAGE: Unable to write root directory entry to datafile. (NMFSERR 2)

Level: NMFSERR 2 CAUSE: This error occurs when NMFILE calls MIDASBUILDROOT when processing an NMCONFOPEN. ACTION: See "File System Error" and "Submitting a CR" at the beginning of this appendix.

MESSAGE: Unable to close datafile. (NMFSERR 3)

Level: NMFSERR 3 CAUSE: FCLOSE failure in MIDASCLOSE, called by NMFILE when processing an NMCONFCLOSE or NMCONFPURGE. ACTION: See "File System Error" and "Submitting a CR" at the beginning of this appendix.

MESSAGE: Unable to open datafile. (NMFSERR 4)

Level: NMFSERR 4 CAUSE: FOPEN failure in MIDASOPEN called by NMFILE when processing an NMCONFOPEN, or an FOPEN failure in MIDASCOMPRESS. File does not exist. ACTION: Create file first. CAUSE: FOPEN failure in MIDASOPEN called by NMFILE when processing an NMCONFOPEN, or an FOPEN failure in MIDASCOMPRESS. File system error. ACTION: See "File System Error" and "Submitting a CR" at the beginning of this appendix.

MESSAGE: Unable to retrieve filecode from datafile. (NMFSERR 5)

Level: NMFSERR 5 CAUSE: This error occurs when NMFILE calls MIDASOPEN which fails on FGETINFO after an NMCONFOPEN was called. This may indicate that the file label has been corrupted. ACTION: See "File System Error" at the beginning of this appendix.

MESSAGE: Datafile does not match user specified filecode. (NMFSWARN 6)

Level: 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 a CR" at the beginning of this appendix.

MESSAGE: Unable to read root directory entry in datafile. (NMFSERR 7)

Level: 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)

Level: 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)

Level: 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 MIDASCRRENAMEPATH (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

MESSAGE: Directory linkage error in datafile. (NMFSERR 10)

Level: 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.

MESSAGE: Unable to read directory entry in datafile. (NMFSERR 11)

Level: 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.

MESSAGE: Data is already associated with this identifier. (NMFSERR 12)

Level: 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.

MESSAGE: Unable to retrieve freespace pointer from datafile. (NMFSERR 13)

Level: 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.

MESSAGE: Filespace exhausted. Unable to add entry. (NMFSERR 14)

Level: 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.

MESSAGE: Unable to write data record to datafile. (NMFSERR 15)

Level: 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.

MESSAGE: Unable to write directory entry to datafile. (NMFSERR 16)

Level: NMFSERR 16 CAUSE: This is due to an FWRITEDIR failure. ACTION: See "File System Error" at the beginning of this appendix.

MESSAGE: No data associated with this identifier. (NMFSERR 18)

Level: NMFSERR 18 CAUSE: In all MIDAS procedures returning this, there is a failure of MIDASFINDENTRY. ACTION: See "File System Error" and "Corrupt Configuration File" at the beginning of this appendix.

MESSAGE: Read truncated to capacity of data buffer. (NMFSWARN 19)

Level: NMFSWARN 19 CAUSE: This error occurs when caller of NMCONFGETDATA specifies a buffer length smaller than the actual data entry size. ACTION: See "Submitting a CR" at the beginning of this appendix.

MESSAGE: Unable to read data record from datafile. (NMFSERR 20)

Level: NMFSERR 20 CAUSE: This error results from a failure of FREADDIR in those MIDAS procedures that call it. (The failure is not an end-of-file found.) ACTION: See "File System Error" at the beginning of this appendix.

MESSAGE: Duplicate identifier already exists. (NMFSERR 21)

Level: NMFSERR 21 CAUSE: This error is returned when trying to add a path that already exists. ACTION: See "File System Error" and "Submitting a CR" at the beginning of this appendix.

MESSAGE: Resultant file size beyond permissible range. (NMFSERR 22)

Level: NMFSERR 22 CAUSE: This error results in MIDASCOMPRESS when the spacebias + maximum file size is greater than 64K. Check the spacebias of MIDASCOMPRESS call in user interface. The file might also be too large or the file label might be corrupt. ACTION: See "File System Error" and "Submitting a CR" at the beginning of this appendix.

MESSAGE: No identifiers exist beyond this path. (NMFSWARN 23)

Level: NMFSWARN 23 CAUSE: This happens when NMCONFnextpath is called and no further path identifiers exist. This may not be an error. Applications calling NMCONFnextpath may use this to find the end of a data branch. Otherwise, it may indicate file corruption. ACTION: See "Submitting a CR" at the beginning of this appendix.

MESSAGE: Pathname exceeds user specified maximum depth. (NMFSERR 24)

Level: NMFSERR 24 CAUSE: This is returned by MIDASPARSEPATH when the user specified pathname is longer than the path depth. No NMCONF procedure calls this intrinsic. ACTION: See "Submitting a CR" at the beginning of this appendix.

MESSAGE: Identifier exceeds maximum permissible length. (NMFSERR 25)

Level: NMFSERR 25 CAUSE: This is returned by MIDASPARSEPATH when the pathname is too long. No NMCONF procedure calls this intrinsic. ACTION: See "Submitting a CR" at the beginning of this appendix.

MESSAGE: Pathname length exhausted user specified buffer. (NMFSERR 26)

Level: NMFSERR 26 CAUSE: This is returned by MIDASTRAVERSE when the maxlevel parameter is exceeded by the pathlevel parameter. This is probably caused by an excessive pathdepth parameter in NMCONF procedure calls. ACTION: See "Submitting a CR" at the beginning of this appendix.

MESSAGE: Unable to rename old datafile prior to replacement. (NMFSERR 27)

Level: NMFSERR 27 CAUSE: This is caused by an FRENAME failure in MIDASCOMPRESS, and is currently only returned by the user interface. ACTION: See "File System Error" at the beginning of this appendix.

MESSAGE: Unable to purge old datafile prior to replacement. (NMFSWARN 28)

Level: NMFSWARN 28 CAUSE: This is due to an FCLOSE failure in MIDAScompress, and is currently returned only by the user interface. ACTION: See "Corrupt Configuration File" at the beginning of this appendix.

MESSAGE: Datafile is empty. (NMFSWARN 29)

Level: NMFSWARN 29 CAUSE: This is returned by MIDAScompress when existing data file has no data in it. This might not be an error if compress is called from the user interface but no data was put into the file. ACTION: If you suspect that there should have been data, then see "Corrupt Configuration File" at the beginning of this appendix.

MESSAGE: Parameter out of range. (NMFSERR 30)

Level: NMFSERR 30 CAUSE: This is a generic error returned from several MIDAS procedures. Check parameters in calls to NMCONF procedures to see if they are in permissible range. ACTION: See "Submitting a CR" at the beginning of this appendix.

MESSAGE: Unable to open message catalog NMCAT.PUB.SYS. (NMFSERR 31)

Level: NMFSERR 31 CAUSE: Returned by MIDASERRMSG if there is a failure to open NMCAT.PUB.SYS. See if this file is on the system. If it is, it might be corrupt. ACTION: See "Invalid Software Installation" at the beginning of this appendix.

MESSAGE: Unable to read message catalog NMCAT.PUB.SYS. (NMFSERR 32)

Level: NMFSERR 32 CAUSE: Returned by MIDASERRMSG. The file might be corrupted. ACTION: See "Invalid Software Installation" at the beginning of this appendix.

MESSAGE: Unable to close message catalog NMCAT.PUB.SYS. (NMFSERR 33)

Level: NMFSERR 33 CAUSE: Returned by MIDASERRMSG. FCLOSE failure on the file. ACTION: See "Submitting a CR" at the beginning of this appendix.

Table-Collapse − Table-Top ↑