X.25 Link Module Configurator Error Codes [ SNA Link/iX Node Manager's Guide ] MPE/iX 5.0 Documentation
SNA Link/iX Node Manager's Guide
X.25 Link Module Configurator Error Codes
Listed below are the error codes that are generated by the X.25 link
module configurator. These messages are displayed on the HP 3000
operator's console. They are listed here in numerical order according to
the ErrorCode displayed as part of these SNA Transport logging messages:
Attempt to close link failed on node NodeName
Subsystem = 734, Error Code = ErrorCode
Attempt to open link failed on node NodeName
Subsystem = 734, Error Code = ErrorCode
The logging messages are described in "SNA Transport Logging Messages"
earlier in this appendix.
-200 MESSAGE CONFIG OPEN ERROR
CAUSE The module configurator encountered an error
while trying to open the configuration file.
ACTION Verify that the NMCONFIG.PUB.SYS configuration
file exists.
--------------------------------------------------------------------------
-201 MESSAGE CONFIG RETRIEVAL ERROR
CAUSE The module configurator encountered an error
while retrieving the SNA/X.25 link configuration
information for the current SNA node.
ACTION Verify that the correct version of NMMGR is
installed on the system, and that an X.25 link
is configured for the SNA node being started.
--------------------------------------------------------------------------
-202 MESSAGE PROCESS CREATION ERROR
CAUSE The module configurator was unable to launch the
Qualified Logical Link Control (QLLC) module.
ACTION Verify that the file containing the QLLC module
(SNAX25.PUB.SYS) exists.
--------------------------------------------------------------------------
-203 MESSAGE TRACE OPEN ERROR
CAUSE The module configurator was unable to open the
trace file.
ACTION Issue the SNACONTROL START command with the
trace file name specified for the LINKTRACE
parameter. If the error still occurs, issue the
SNACONTROL START command without specifying a
trace file name (that is, let the default file
name be used). If the error still occurs, call
your Hewlett-Packard support contact.
--------------------------------------------------------------------------
-204 MESSAGE STATUS BUFFER INVALID
CAUSE The Qualified Logical Link Control (QLLC) module
returned an invalid buffer containing the link
status information. Note that the node can
still function, but link status information
cannot be retrieved.
ACTION Call your Hewlett-Packard support contact.
--------------------------------------------------------------------------
-205 MESSAGE STATUS REPLY INVALID
CAUSE The module configurator status routine received
an invalid status reply. Note that the node can
still function, but link status information
cannot be retrieved.
ACTION Call your Hewlett-Packard support contact.
--------------------------------------------------------------------------
-500 MESSAGE UNABLE TO RECEIVE OPENLINK COMPLETION MESSAGE
CAUSE The module configurator encountered an error
while trying to receive the OpenLink completion
message.
ACTION Call your Hewlett-Packard support contact.
--------------------------------------------------------------------------
-501 MESSAGE UNABLE TO GET MSG FRAME FOR CLOSELINK REQUEST
CAUSE The module configurator encountered an error
while trying to allocate the CloseLink request
message.
ACTION Call your Hewlett-Packard support contact.
--------------------------------------------------------------------------
-502 MESSAGE UNABLE TO SEND CLOSELINK REQUEST
CAUSE The module configurator encountered an error
while trying to send the CloseLink request
message.
ACTION Call your Hewlett-Packard support contact.
--------------------------------------------------------------------------
-503 MESSAGE UNABLE TO RECEIVE CLOSELINK COMPLETION MESSAGE
CAUSE The module configurator encountered an error
while trying to receive the CloseLink completion
message.
ACTION Call your Hewlett-Packard support contact.
--------------------------------------------------------------------------
-504 MESSAGE UNABLE TO GET MSG FRAME FOR TRACE ENABLE REQUEST
CAUSE The module configurator encountered an error
while trying to allocate the trace enable
request message.
ACTION Call your Hewlett-Packard support contact.
--------------------------------------------------------------------------
-505 MESSAGE UNABLE TO SEND TRACE ENABLE REQUEST
CAUSE The module configurator encountered an error
while trying to send the trace enable request
message.
ACTION Call your Hewlett-Packard support contact.
--------------------------------------------------------------------------
-506 MESSAGE UNABLE TO SEND TRACE DISABLE REQUEST
CAUSE The module configurator encountered an error
while trying to send the trace disable request
message.
ACTION Call your Hewlett-Packard support contact.
--------------------------------------------------------------------------
-507 MESSAGE UNABLE TO GET MESSAGE FRAME FOR TRACE DISABLE
REQUEST
CAUSE The module configurator encountered an error
while trying to allocate the trace disable
request message.
ACTION Call your Hewlett-Packard support contact.
--------------------------------------------------------------------------
-508 MESSAGE UNABLE TO GET MESSAGE FRAME FOR STATUS REQUEST
CAUSE The module configurator encountered an error
while trying to allocate the status request
message.
ACTION Call your Hewlett-Packard support contact.
--------------------------------------------------------------------------
-509 MESSAGE UNABLE TO SEND STATUS REQUEST
CAUSE The module configurator encountered an error
while trying to send the status request message.
ACTION Call your Hewlett-Packard support contact.
--------------------------------------------------------------------------
-510 MESSAGE UNABLE TO RECEIVE STATUS COMPLETION MESSAGE
CAUSE The module configurator encountered an error
while trying to receive the status completion
message.
ACTION Call your Hewlett-Packard support contact.
--------------------------------------------------------------------------
MPE/iX 5.0 Documentation