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

Chapter 21 495
Logging Location Codes
Control Process Logging Location Codes
289 CLAS0003 MESSAGE: INTERNAL ERROR; NM Entry
CAUSE: While creating a network NI for which IP Store and Forward
was enabled, NETCP was unable to put the new Store and Forward
buffer pool ID into a new entity, having the same name as the NI, 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 a CR,” of
this manual.
290 CLAS0003 MESSAGE: INTERNAL ERROR; NM Entry
CAUSE: During NETCP’s early initial startup, it was unable to put the
NETCP utility buffer pool ID into a new entity named “CP POOL” 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 a CR,” of
this manual.
291 CLAS0003 MESSAGE: INTERNAL ERROR; NM Entry
CAUSE: While creating an NI because a network was being started,
NETCP was unable to put that NI outbound buffer pool ID into a new
entity, having the same name as the NI, 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 a CR,” of
this manual.
292 CLAS0002 MESSAGE: BUFFER MANAGER; Buffer manager error
CAUSE: While building a buffer containing all X25 configuration data
for a network, NETCP successfully obtained a buffer of the supposedly
correct size, but later encountered an error attempting to write a block
of Network Directory address information to the buffer (PARM = 32-bit
status returned by the call to bmgr_write_buffer).
ACTION: 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.