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

Appendix A 209
NMS Error Messages
NMFS Error and Warning Messages
ACTION: See “Submitting an SR” at the beginning of this appendix.
MESSAGE: Identifier exceeds maximum permissible length.
(NMFSERR 25)
NMFSERR 25 CAUSE: This is returned by MIDASPARSEPATH when the pathname
is too long. No NMCONF procedure calls this intrinsic.
ACTION: See “Submitting an SR” at the beginning of this appendix.
MESSAGE: Pathname length exhausted user specified buffer.
(NMFSERR 26)
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 an SR” at the beginning of this appendix.
MESSAGE: Unable to rename old datafile prior to replacement.
(NMFSERR 27)
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)
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)
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)
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 an SR” at the beginning of this appendix.