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

Chapter 19 349
Logging Location Codes
Control Process Logging Location Codes
possible too much frozen memory is being used by the system, but this
can change with time. Use GLANCEXL or a similar utility to check
memory usage by the system. If these are not the causes and the
problem persists even if retried after a suitable waiting period,
seeAppendix A, “Submitting an SR,” of this manual.
MESSAGE: INTERNAL ERROR; NM Entry
406 CLAS0003 CAUSE: While creating a frozen inbound buffer pool for a particular NI
device because its network was being started, NETCP was unable to
put that pool ID into a new entity, having a name that is the ASCII
version of the decimal buffer size, in the NS Registry (PARM = 32-bit
status returned by the call to reg_add_entity).
ACTION: This error was not fatal, and startup continued; use of the
Registry here is not critical. However, creation of the NS Registry by
NETCP may have failed (see error 285), or the Registry may be full. If
the message occurs every time, see Appendix A, “Submitting an SR,” of
this manual.
MESSAGE: INTERNAL ERROR; Device open
407 CLAS0002 CAUSE: While attempting to start a LAPB PSI device on an existing NI,
NETCP was unable to create a frozen inbound buffer pool for that
device's reads (PARM = 32-bit status returned by the call to
cp_get_read_pool). Always preceded by another error indicating the
original failure (see error 404).
ACTION: The device did not start. Check the packet size configured in
the NMCONFIG file; for LAPB links, pool creation parameters are
obtained from this file. Depending on the error, it is possible too much
frozen memory is being used by the system, but this can change with
time. Use GLANCEXL or a similar utility to check memory usage by
the system. If these are not the causes and the problem persists even if
retried after a suitable waiting period, see Appendix A, “Submitting an
SR,” of this manual.
MESSAGE: INTERNAL ERROR; Device close
410 CLAS0002 CAUSE: While shutting down a specific protocol on a network, NETCP
encountered an error attempting to unbind that protocol from a device
driver (PARM = 32-bit status returned by the call to
ns_separate_from_driver). NETCP did not expect any error since it
supposedly bound that protocol to the driver during network startup.
(Some pre-5.0 versions of Transport also reported unbind errors for
shutdown of specific devices under this location; now see error 673).
ACTION: This error in itself was not failed, and protocol shutdown
continued. If this error occurs every time, see Appendix A, “Submitting
an SR,” of this manual.