SNA over TCP/IP storage has been exhausted and MPTN function is no longer available. Communication is no longer possible using SNA over TCP/IP connections; however, native APPC communication may still be available.
USER RESPONSE:
To reactivate SNA over TCP/IP function, stop Communications Manager/2 and then restart it using normal procedures. If the problem persists, call IBM for service.
EEXPLANATION:
A critical SNA over TCP/IP internal error has occurred. Communication is no longer possible using SNA over TCP/IP connections; however, native APPC communication may still be available.
USER RESPONSE:
To reactivate SNA over TCP/IP function, stop Communications Manager/2 and then restart it using normal procedures. If the problem persists, call IBM for service.
For detailed information, use FFST/2 to access the system error log and review the associated error log. Use the date, time, and problem ID to locate the appropriate system error log entry.
EEXPLANATION:
An unexpected internal condition was detected that is considered a noncritical error. An SNA over TCP/IP connection may have failed or have been closed.
USER RESPONSE:
If a connection failed, attempt to restart it.
For detailed information, use FFST/2 to access the system error log and review the associated error log. Use the date, time, and problem ID to locate the appropriate system error log entry.
EEXPLANATION:
An MPTN configuration or definition error was logged because:
00000004-00010004: the configuration file MPTNCMM.CFN could not could not be opened
00000004-00010005: there is an error in the MPTNCMM.CFN file
00000004-00010008: the Communications Manager/2 trace facilities could not be loaded
00000004-00010009: SNA over TCP/IP could not load TCP/IP
00000004-0001000A: SNA over TCP/IP could not load APPC
00000004-000C0003: an error was detected in an SNA over TCP/IP environment variable
USER RESPONSE:
For detailed information, use FFST/2 to access the system error log and review the associated error log. Determine the cause based on the minor codes listed above. Use the date, time, and problem ID to locate the appropriate system error log entry. Determine the cause based on the error codes listed above.
For problems with the file MPTNCMM.CFN, call IBM for service.
EEXPLANATION:
The SNA over TCP/IP connection setup attempt failed because:
00000005-00030001: no route was available to the partner
00000005-00030002: the partner node may be down, TCP/IP may not be running in the partner node, SNA over TCP/IP may not be active in the partner node, or the partner may be overloaded by connection requests
00000005-00030003: local resources, such as available sockets, have been temporarily exhausted
00000005-00030004: there was a failure in the TCP/IP connection setup process
00000005-00030005: there was a failure in the TCP/IP connection setup process
00000005-00030006: there was a temporary shortage of TCP/IP buffers
00000005-00030007: all the gateways that can be used to access the partner have reached their connection limits
USER RESPONSE:
Retry the connection request.
For detailed information, use FFST/2 to access the system error log and review the associated error log. Use the date, time, and problem ID to locate the appropriate system error log entry. Determine the cause based on the codes listed above.
EEXPLANATION:
An established SNA over TCP/IP connection failed because:
00000006-00050001: the partner TCP/IP closed the connection
00000006-00050002: the partner node is not available
00000006-00050003: there was an MPTN protocol error
00000006-00050004: there was a temporary shortage of TCP/IP buffers
00000006-00050005: there was a temporary shortage of SNA over TCP/IP buffers
USER RESPONSE:
Attempt to restart the connection.
For detailed information, use FFST/2 to access the system error log and review the associated error log. Use the date, time, and problem ID to locate the appropriate system error log entry. Determine the cause based on the codes listed above.
EEXPLANATION:
An MPTN connection setup attempt failed because:
00000007-000040001: the partner address (LU name) was not reachable in the destination node
00000007-000040002: although the partner address was found in the destination node, it was not ready to accept the connection request
00000007-000040003: the partner rejected the connection request
00000007-000040004: the request was rejected by SNA over TCP/IP in the partner node
USER RESPONSE:
Attempt to restart the connection.
For detailed information, use FFST/2 to access the system error log and review the associated error log. Use the date, time, and problem ID to locate the appropriate system error log entry. Determine the cause based on the codes listed above.
EEXPLANATION:
There was a protocol violation.
USER RESPONSE:
Determine whether the partner node is equipped with compatible SNA over TCP/IP capabilities.
For detailed information, use FFST/2 to access the system error log and review the associated error log. Use the date, time, and problem ID to locate the appropriate system error log entry.
EEXPLANATION:
There was a protocol violation.
USER RESPONSE:
Determine whether the partner node is equipped with compatible SNA over TCP/IP capabilities. Apply any corrective service package that might be applicable.
For detailed information, use FFST/2 to access the system error log and review the associated error log. Use the date, time, and problem ID to locate the appropriate system error log entry.
EEXPLANATION:
An installation error occurred because:
0000000A-000010006: SNA over TCP/IP could not load TCP/IP
0000000A-000010007: SNA over TCP/IP could not load APPC
USER RESPONSE:
For detailed information, use FFST/2 to access the system error log and review the associated error log. Use the date, time, and problem ID to locate the appropriate system error log entry.
Determine the cause based on the codes listed above.
Ensure that TCP/IP code can be loaded and initialized.
Ensure that the APPC code can be loaded and initialized.
Ensure that the configuration file MPTNCMM.CFN exists in the CMLIB directory and that it has not been corrupted. If it has been corrupted, restore the file from backup or reinstall SNA over TCP/IP.
EEXPLANATION:
TCP/IP is not installed, or not started.
USER RESPONSE:
Ensure that TCP/IP has been installed, and has been started. If TCP/IP is started after Communications Manager/2, ensure that the time interval between when APPC is started and when TCP/IP is started, does not exceed the time interval (in minutes) defined in the environment variable TCPWAIT_MINS. If this environment variable is not defined in CONFIG.SYS, the default time interval is 15 minutes.
EEXPLANATION
The local resource limit has been exceeded because of one of the following reasons:
0000000C-00090001: No more sockects are available to create TCP connections or send datagrams.
0000000C-00090002: No more threads can be created.
0000000C-0001000B: SNA over TCP/IP storage for out-of-band (OOB) datagrams (expedited data) has been exhausted.
USER RESPONSE:
Free up the exhausted resource by reducing the number of active connections or application programs that are running.
EEXPLANATION
An internal function was requested that is not supported.
USER RESPONSE:
Call IBM for service.
For detailed information, use FFST/2 to access the system error log and review the associated error log. Use the date, time, and problem ID to locate the appropriate system error log entry.
EEXPLANATION
The TCP/IP domain name server could not be located.
USER RESPONSE:
Ensure that a domain name server is accessible within the TCP/IP network. See the TCP/IP documentation
describing the use of the RESOLV file.
WEXPLANATION
The specified LU name could not be found in the TCP/IP domain name server.
USER RESPONSE: Ensure that the mapping from the destination LU name to the IP address where the LU resides is entered in the database of a domain name server that is accessible from the node where this error was logged.
The SNA over TCP/IP feature has loaded successfully. SNA over TCP/IP connections will be available after APPC and TCP/IP is initialized.
USER RESPONSE:
None.
EEXPLANATION
One or more socket application programs are using the well known port number (397) that is reserved for SNA over TCP/IP.
USER RESPONSE: This port number is reserved and should not be used by any other application program. Remove the application programs using port number 397. They cannot coexist with SNA over TCP/IP in the same TCP/IP network.
WEXPLANATION
Too much time elapsed without a response to an MPTN connection request.
USER RESPONSE:
Check the network for any problems. Ensure that the intended partner is reachable. If necessary, increase the CONN_RETRY_SECS environment variable.
IEXPLANATION
Either one or more of the MPTN DLLS (MPTNCMM, or TCPPMM, or LUTAB, or ACSMPTN, or ANUTIL) are missing or corrupted.
USER RESPONSE: Reinstall MPTN.
EEXPLANATION
An out-of-band datagram contained a connection alias or a connection identifier that does not correspond to an existing connection. The connection was probably removed by the receiving side because it thought that the partner was inoperative.
USER RESPONSE: This condition may occur in the system, and no user response is necessary.
IEXPLANATION
SNA over TCP/IP has failed to initialize correctly.
USER RESPONSE: The message log and system error log may contain more
details about the initialization failure. Note the timestamp on this
message and investigate the message with timestamps close to this one.
IEXPLANATION
SNA over TCP/IP has failed to initialize correctly. The configuration file was
defined for the gateway product, but the module MPTNCMM.DLL does not have
gateway functionality.
USER RESPONSE: This is probably caused by an installation error. Reinstall.
IEXPLANATION
The gateway has reached the limit of the number of connections it can support.
USER RESPONSE: If you do not have the highest connection limit tier, purchase
a higher tier for the gateway, get a new password, and reinstall the gateway.
If you have the highest tier, install one or more parallel gateways.
(.txt)