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

518 Chapter21
Logging Location Codes
Control Process Logging Location Codes
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.
647 CLAS0003 MESSAGE: INTERNAL ERROR; Module Deconfig Failed
CAUSE: While shutting down an NI due to a system shutdown or a
:NETCONTROL STOP command, NETCP encountered an error while
trying to stop one of the NI specific protocols for that network (PARM =
32-bit escape code returned by the call to the module deconfigurator
that failed). Always preceded by another error from another entity
(having a different Entity number, such as 151–160), indicating the
cause of the original failure.
ACTION: This error in itself was not fatal, and shutdown continued.
However, some system resources may be lost until the next system
restart. Inspect the previous error, and if necessary see Appendix A ,
“Submitting a CR,” of this manual.
648 CLAS0002 MESSAGE: BUFFER MANAGER; Buffer manager error
CAUSE: While reading the home node’s path report during initial
NETCP startup, or while starting some network specific protocols for a
LAN, GATEHALF or ROUTER network because a :NETCONTROL
command was issued, NETCP successfully read local node name data
from the NMCONFIG file, then encountered an error trying to write
that data into a buffer it obtained a short time earlier (PARM = 32-bit
status returned by the call to bmgr_write_buffer).
ACTION: NETCP was unable to write all the required data, and
attempted to recover and free the buffer. The network operation that
was being performed will not work correctly. Because the buffer given to
NETCP by the buffer manager should have been large enough to
contain all data that was to be written, there may be a problem in
either NETCP, the buffer manager, the NMS subsystem, or NMMGR, or
the NMCONFIG file may be corrupt. Stop the network and retry the
operation. If the problem persists, see Appendix A , “Submitting a CR,”
of this manual.
649 CLAS0002 MESSAGE: Bad status
CAUSE: After successfully building a buffer containing needed
configuration data for an X25 network that was being started, NETCP
encountered an error trying to send the buffer to the X25 protocol
module (PARM = 32-bit status returned by the call to send_msg).
ACTION: X25 did not receive its configuration data, though the rest of
network startup continued. The X25 network will not operate correctly
in this condition. In addition, the buffer may have been lost, which may
result in error 613 when the network is stopped. Try stopping and