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

270 AppendixA
Messages
LAN Error Messages
228 MESSAGE: Could not open NMCONFIG.PUB.SYS file.
CAUSE: The configuration file NMCONFIG.PUB.SYS was purged or
renamed or the NMCONFIG.PUB.SYS configuration file may be opened
with exclusive access.
ACTION: Type a LISTF NMCONFIG.PUB.SYS to determine if the file has
been opened with exclusive access. If it has, wait for the program or
process that has this file opened exclusively to close it.
If the configuration file is missing, restore the file from a backup tape
and restart the link again.
CAUSE: The configuration file NMCONFIG.PUB.SYS may be opened with
exclusive access.
ACTION: Wait for the program or process that has this file opened
exclusively to close it.
229 MESSAGE: Link data not found in NMCONFIG.PUB.SYS.
CAUSE: The link data is not found in the configuration file
NMCONFIG.PUB.SYS.
ACTION: Use NMMGR to create the link data for the link you are trying
to start. Try to start the link again.
230 MESSAGE: The link data record is incorrect for this driver.
CAUSE: The link data record is corrupted in the configuration file
NMCONFIG.PUB.SYS.
ACTION: Restore the file from a backup tape and restart the link again.
CAUSE: The configuration file NMCONFIG.PUB.SYS was not converted to
a version supported by the driver.
ACTION: Run NMMGRVER on the configuration file
NMCONFIG.PUB.SYS.
233 MESSAGE: A call to IO_GET_MGR_ENTRY failed during driver
configuration.
CAUSE: Unknown. Need more information.
ACTION: Write down the error information displayed on the console and
call your Hewlett-Packard support contact.
234 MESSAGE: A call to IO_CONFIG failed during driver configuration.
CAUSE: Wrong physical path is configured for the installed LAN card.
ACTION: Use NMMGR to correct the Physical Path for the link.
CAUSE: The card for the configured path is bad.
ACTION: To determine whether the LAN card is good your
Hewlett-Packard representative must run diagnostics on the LAN card.