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
198 AppendixA
Messages
SNACONTROL Error Messages
SNACIERR 9 MESSAGE: NODE SPECIFIED NOT ACTIVE. (SNACIERR 9)
CAUSE: An SNACONTROL command was issued for an SNA node that is
not active. The node either was never started or has been stopped.
ACTION: Issue the SNACONTROL STATUS command to see whether the
node is active. If the node is not active, issue the SNACONTROL START
command for the node. Once the node is active, reissue the first
SNACONTROL command. If the error still occurs, write down the
circumstances and call your Hewlett-Packard support contact.
SNACIERR 10 MESSAGE: NODE SPECIFIED IS ALREADY ACTIVE. (SNACIERR 10)
CAUSE: The SNACONTROL START command was issued for a node that is
already active.
ACTION: Ensure that you are specifying the correct
NodeName
in the
SNACONTROL START command.
SNACIERR 11 MESSAGE: NODE SPECIFIED NOT CONFIGURED. (SNACIERR 11)
CAUSE: No configuration data was found for the SNA node specified in
the command.
ACTION: Use NMMGR or the configuration file critical summary to
verify that the configuration file NMCONFIG.PUB.SYS contains data for
the specified node. If it does, ensure that the SNACONTROL command was
issued correctly.
SNACIERR 12 MESSAGE: MORE THAN ONE NODE IN CONFIGURATION. PLEASE
SPECIFY. (SNACIERR 12)
CAUSE: An SNACONTROL command was issued without a
NodeName
parameter. Since more than one node is configured, the
NodeName
must
be specified.
ACTION: Reissue the command with the correct
NodeName
specified.
SNACIERR 13 MESSAGE: NO SNA NODE IS CONFIGURED IN NMCONFIG.PUB.SYS.
(SNACIERR 13)
CAUSE: An SNACONTROL START command was issued without a
NodeName
parameter. If this is done when the configuration file
(NMCONFIG.PUB.SYS) contains data for only one node, that node is
started, by default. However, no node data was found in the
configuration file when the command was issued. So, the default could
not be used.
ACTION: Use NMMGR or the configuration file critical summary to
verify that the configuration file contains data for at least one SNA
node. If it does, ensure that the SNACONTROL START command was
issued correctly. If the configuration file does not contain data for at
least one node, configure the appropriate node and then reissue the
SNACONTROL START command.