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

204 AppendixA
NMS Error Messages
NM Error Messages
MESSAGE: Total data length too large to return as integer.
(NMERR 221)
NMERR 221 CAUSE: Returned by NMCONFSONINFO. The total data length
associated with the path name and all its first level sons was greater
than 32767 and could not be returned to caller. It is possible that the
configuration file is corrupt. It is also possible that there is no error at
all. It is theoretically possible, although unlikely, to have more than
32767 bytes of data associated with a path and its first level sons.
ACTION: See “Corrupt Configuration Files” at the beginning of this
appendix.
CAUSE: Possible internal error.
ACTION: See “Submitting an SR” at the beginning of this appendix.
MESSAGE: Son count too large to return as integer. (NMERR 222)
NMERR 222 CAUSE: Returned by NMCONFSONINFO. The number of first level
sons linked to the path name sent by the calling subsystem exceeds
32767. It is possible that the configuration file is corrupt. It is also
possible that an internal error occurred.
ACTION: See “Getting Help” at the beginning of this appendix.
MESSAGE: Request type out of bounds — error in port msg to
NMFILE. (NMERR 223)
NMERR 223 CAUSE: Returned if NMFILE receives a request type that it does not
recognize as being a valid NMCONF intrinsic request on its NMCONF
subqueue.
ACTION: Internal error. See “Getting Help” at the beginning of this
appendix.
MESSAGE: Will use LOGGING configuration for this subsystem that
is already active. (NMERR 301)
NMERR 301 CAUSE: Returned by NMOPENLOG, NMOPENLOG2. The open log
was successful and logging may proceed. Note that there is another
openlog outstanding for the same subsystem id, so the configuration
information already in use will continue to be used. This result code is
returned as a negative number (-301) to indicate it is not an error and
that the openlog was in fact successful.
ACTION: None.