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

Chapter 21 529
Logging Location Codes
Control Process Logging Location Codes
684 CLAS0002 MESSAGE: BUFFER MANAGER; Buffer manager error
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 a CR,” of this manual.
685 CLAS0002 MESSAGE: BUFFER MANAGER; Buffer manager error
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
encountered an error trying to read other data entries to match up to
the first one (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; since it already read once, this indicates a probable bug in
NETCP. Stop the network and retry the operation. If the problem
persists, see Appendix A , “Submitting a CR,” of this manual.
686 CLAS0002 MESSAGE: BUFFER MANAGER; Buffer manager error
CAUSE: After successfully opening the NSDIR network directory file,
while preparing to read X25 network directory information from the
file, NETCP was unable to obtain a buffer from its own buffer pool large
enough to hold the maximum possible number of X25 mapping entries
(PARM = 32-bit status returned by the call to bmgr_get_buffer). The
size of the buffer NETCP tried to obtain was based on the size of the
mapping table, a value which was obtained from a hidden field in the
NI record of the NMCONFIG file.
ACTION: No network directory data was read, and NETCP attempted to
recover and close the opened file. Some versions of transport may then
attempt to build X25 mappings, even though no buffer was obtained,
and send a restart message to X25. After the error, network startup
may continue to completion, but the resulting network will probably not