HP 3000 Manuals

NMFSWARN Messages [ Using the Node Management Services (NMS) Utilities ] MPE/iX 5.0 Documentation


Using the Node Management Services (NMS) Utilities

NMFSWARN Messages 

NMFSWARN messages are produced by the NMS File Server (NMFILE.PUB.SYS).
In most cases, they are accompanied by other messages (NMGRERRs or MPE
File System errors); you should take the action documented for the
accompanying messages first.

NMFSWARN 6   MESSAGE      Datafile does not match user specified filecode.

                          (NMFSWARN 6)

             CAUSE        This warning happens when NMFILE calls MIDASOPEN
                          and the file code parameter of NMCONFOPEN does
                          not match the file code of the data file.  The
                          data file specified is not a configuration file.

             ACTION       Check that you specified a file of the correct
                          file type (NCONF). Check the spelling of the
                          file name.

             CAUSE        The data file label is corrupt.

             ACTION       See "Corrupt Configuration File" and "Submitting
                          an SR" at the beginning of this appendix.

--------------------------------------------------------------------------

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

             CAUSE        This error occurs when a data length longer than
                          8192 bytes is specified in a call to
                          MIDASGETDATA. The parameters to MIDASGETDATA
                          and/or NMCONFGETDATA may be invalid.  Internal
                          error.

             ACTION       See "Submitting an SR" at the beginning of this
                          appendix.

--------------------------------------------------------------------------

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

             CAUSE        This happens when MIDASNEXTPATH 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 a corrupt file.

             ACTION       See "File System Error" and "Submitting an SR"
                          at the beginning of this appendix.

--------------------------------------------------------------------------

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

             CAUSE        This is due to an FCLOSE failure in
                          MIDASCOMPRESS. This is currently returned only
                          by user interface.

             ACTION       See "File System Error" at the beginning of this
                          appendix.

--------------------------------------------------------------------------

NMFSWARN 29  MESSAGE      Datafile is empty.  (NMFSWARN 29)

             CAUSE        This is returned by MIDASCOMPRESS when the
                          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 the user suspects that there should have been
                          data, then see "Corrupt Configuration File" at
                          the beginning of this appendix.

--------------------------------------------------------------------------



MPE/iX 5.0 Documentation