NS3000/iX Error Messages Reference Manual (36923-90043)

Chapter 21 501
Logging Location Codes
Control Process Logging Location Codes
host. This error message is only printed once per startup, even if
multiple X25 addresses have this problem.
412 CLAS0002 MESSAGE: INTERNAL ERROR; Internal resource error
CAUSE: NETCP received an unrecognized message on port subqueue 2
or 4, which are only designed for asynchronous event messages
(PARM = first 16 bits of message, which should give the message type.)
NETCP was expecting either a DCLDM event message (type 340) or an
SDI async event message (type 390).
ACTION: This error in itself was not fatal, and NETCP continued
operating. However, some other modules on the system may still be
waiting for a message exchange that mistakenly went to NETCP, and
this could cause problems in those other modules. If disc logging was
enabled, NETCP logged the entire received message to the current NM
logfile, which may aid in diagnosis. It may not have been a Transport
message at all. If necessary, see Appendix A , “Submitting a CR,” of this
manual.
413 CLAS0002 MESSAGE: BUFFER MANAGER; Buffer manager error
CAUSE: While collecting configuration data for startup of an X25
network, NETCP successfully obtained a buffer to hold the data, but
later on was unable to write data into that buffer (PARM = 32-bit status
returned by the call to bmgr_write_buffer).
ACTION: Not all the configuration data was collected, and startup of
that network failed. Check the configuration file using NMMGR, to see
that the amount of X25 configuration data seems to be within limits.
Also verify your system has any and all software patches that may be
needed to use the amount of X25 configuration data you are specifying.
If the problem still cannot be isolated, see Appendix A , “Submitting a
CR,” of this manual.
414 CLAS0002 MESSAGE: INTERNAL ERROR; Internal resource error
CAUSE: NETCP received an asynchronous DCLDM event message, but
the device number in the message did not correspond to any known
device in NETCP’s tables (PARM = 16-bit internal ldev number from
the message).
ACTION: This error in itself was not fatal, and NETCP continued
operating. Some kind of timing condition may have occurred. Another
possibility is NETCP or a DCLDM may be confused. If the problem
occurs repeatedly, see Appendix A , “Submitting a CR,” of this manual.
416 CLAS0002 MESSAGE: INTERNAL ERROR; Async request from link
CAUSE: NETCP received an asynchronous SDI event message, but the
specific type of event was something other than an exception event, the
only message type NETCP was expecting (PARM = 32-bit SDI status
field from the message).