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

378 Chapter19
Logging Location Codes
Control Process Logging Location Codes
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, NMMGR, or the NMCONFIG file may be corrupt. Use
NMMGR to check the X25 configuration in the file. Stop the network
and retry the operation. If the problem persists, see Appendix A,
“Submitting an SR,” of this manual.
MESSAGE: BUFFER MANAGER; Buffer manager error
683 CLAS0002 CAUSE: While reading X25 configuration data because a :NETCONTROL
command was issued, NETCP successfully computed the size of all
applicable X25 data in the NMCONFIG file, then encountered an error
trying to write a small descriptive header onto the start of a a buffer it
obtained a short time earlier to hold all the X25 configuration data
(PARM = 32-bit status returned by the call to bmgr_write_buffer).
ACTION: No X25 data was actually buffered, and NETCP attempted to
recover and free the buffer. Though startup of that X25 network
probably continued, the network will not operate 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,
NMMGR, or the NMCONFIG file may be corrupt. Stop the network and
retry the operation. If the problem persists, see Appendix A,
“Submitting an SR,” of this manual.
MESSAGE: BUFFER MANAGER; Buffer manager error
684 CLAS0002 CAUSE: After NETCP successfully wrote configuration data for an X25
network into a buffer it obtained earlier, because a :NETCONTROL
command was issued, while trying to crossmatch the X25 mappings
NETCP encountered an error trying to read a data entry out of that
same buffer (PARM = 32-bit status returned by the call to
bmgr_read_buffer).
ACTION: The current matching operation stopped, then more merging
of X25 mappings may have continued, possibly causing more errors,
then the bad configuration data was passed to the X25 protocol module.
The X25 network will probably not operate correctly now. Because
NETCP already wrote to the buffer, it should have also been able to
read from it; probable causes are a bug in NETCP or in the buffer
manager. Stop the network and retry the operation. If the problem
persists, see Appendix A, “Submitting an SR,” of this manual.
MESSAGE: BUFFER MANAGER; Buffer manager error
685 CLAS0002 CAUSE: After NETCP successfully wrote configuration data for an X25
network into a buffer it obtained earlier, because a :NETCONTROL
command was issued, while trying to crossmatch the X25 mappings
NETCP successfully read one data entry out of that buffer, then