SNA Link/iX Node Managers Guide (30291-90009)
Table Of Contents
- 1 SNA Links Overview
- 2 SNA Node and Link Configuration
- 3 Logging Configuration
- 4 SNA Node Startup and Shutdown
- 5 SNA Link Troubleshooting
- 6 MPE Commands
- 7 SNA Link Installation Information
- A Messages
- SDLC Link Startup Error Messages
- SDLC Link Driver Error Messages
- SNACONTROL Error Messages
- SNA Transport Error Messages
- SNA Transport Logging Messages
- SDLC Link Shutdown Error Messages
- X.25 Link Failure Error Codes
- X.25 Link Module Configurator Error Codes
- X.25 Link QLLC Internal Error Codes
- NetView Alerts Error Messages
- Network Dump Manager Error Messages
- LAN Error Messages
- B Netview Alerts

190 AppendixA
Messages
SDLC Link Driver Error Messages
driver did not find its own subsystem number in the expected buffer
field.
ACTION: Run NMMAINT to verify that the software versions between
the driver (WANSDLCVERS) and module configurator (WANMCVERS)
are correct. Also check your configuration screens, and if necessary,
restore NMCONFIG.PUB.SYS from a system backup tape. If the problem
continues, call your Hewlett-Packard support contact.
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 of 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 a trace, try specifying a
larger trace buffer size. A version mismatch between your driver
(WANSDLCVERS) and other supporting software might exist; call your
Hewlett-Packard support contact.
1058 MESSAGE: Driver tracing is already off.
CAUSE: The driver received a trace disable request when tracing was
already off. The trace manager module should not have passed the
request to the driver when tracing was off.
ACTION: This is intended as a warning. You do not have to turn tracing
off when it is not on.
1059 MESSAGE: Driver tracing is already on.
CAUSE: The driver received a trace enable request when tracing was
already on. The trace manager module should not have passed the
request to the driver when tracing was on. The driver does not support
altering the active trace level in this way.
ACTION: This is intended as a warning. You cannot turn tracing on
when it is already on.
1060 MESSAGE: Bad download file address in configuration data.
CAUSE: The memory address of an open download file must be in a
configuration buffer passed during startup. However, the driver found
an address of zero, which is an invalid address. The module
configurator should not have sent the configure message if it could not
open the download file. Also, configuration buffer formats might be
mismatched.
ACTION: Run NMMAINT to verify the versions of the driver
(WANSDLCVERS), module configurator (WANMCVERS), and
download file (PSISDLC0.PUB.SYS or PSISDLC1.PUB.SYS). If the
problem cannot be solved by using this information, call your
Hewlett-Packard support contact.