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

Chapter 20 453
LAP-B Link Error Messages
LAP-B Link Driver Error Messages
1057 MESSAGE: Input buffer passed in a message is too small.
CAUSE: Data was requested from the driver but the length of the buffer
specified in the request was too small to accept all the data. The driver
is not capable of returning partial data. The driver also imposes a
minimum-size limit on trace buffers.
ACTION: If the problem occurred when starting trace, try specifying a
larger trace buffer size. There may be a version-mismatch between your
driver and other supporting software; call your Hewlett-Packard
representative.
1058 MESSAGE: Driver tracing is already off.
CAUSE: The driver received a trace disable request when trace was
already off. The trace manager module should not have passed the
request to the driver when trace was off.
ACTION: This is intended as a warning. You do not need to turn trace off
when it is not on.
1059 MESSAGE: Driver tracing is already on.
CAUSE: The driver received a trace enable request when trace was
already on. The trace manager module should not have passed the
request to the driver when trace was on. The driver does not support
altering the active trace level in this manner.
ACTION: This is intended as a warning. You cannot turn trace on when
it is already on.
1060 MESSAGE: Bad download file address in configuration data.
CAUSE: The driver requires the valid memory address of an open
download file to appear in a configuration buffer passed during startup,
but the address it found was zero. The module configurator should not
have sent the configure message if it could not open the download file.
Alternately, configuration buffer formats may be mismatched.
ACTION: Run NMMAINT.PUB.SYS to verify the versions of the driver,
module configurator, and download file. If the problem cannot be solved
from this information, call your Hewlett-Packard representative.
1061 MESSAGE: Bad middle plane buffer pool in configuration data.
CAUSE: The driver requires the valid buffer-pool ID of a pool to be used
for read/write datacomm line frames, to appear in a configuration
buffer passed during startup, but the ID it found was zero. The
transport should not have invoked the module configurator if the buffer
pool could not be opened. Alternately, configuration buffer formats may
be mismatched.
ACTION: Check to see if the transport reported any initialization errors.
Run NMMAINT.PUB.SYS to verify the versions of the driver, module
configurator, and download file. If the problem cannot be solved from