Analysis
Table 1 shows symptoms of session outages and refers to the steps needed for initial diagnosis of the error.
| If this is the outage type | Then perform these steps |
|---|---|
| TCP/IP session outage | If the TCP/IP console shows a TCP/IP
error message, see z/OS Communications Server: IP Messages Volume 2 (EZB, EZD) and follow the directions for system programmer
response for the message. If TCP/IP abended, see Diagnosing abends, loops, and hangs. |
| SNALINK LU0 session outage | If the SNALINK LU0 console shows
a SNALINK error, see the explanation of the corresponding error message
as described in z/OS Communications Server: IP Messages Volume 1 (EZA) or z/OS Communications Server: SNA Messages. For more information about diagnosing SNALINK LU0 session outages, see Diagnosing SNALINK LU0 problems. |
| NCPROUTE-to-NCP client session outage | If the NCPROUTE console shows an NCPROUTE error message, see z/OS Communications Server: IP Messages Volume 2 (EZB, EZD) and follow the directions for system programmer response for the message. |
| NCPROUTE-to-SNMP agent session outage | If the SNMP agent console shows an SNMP error
message, see z/OS Communications Server: IP Messages Volume 2 (EZB, EZD) and follow the directions for system programmer
response for the message. For more information about diagnosing SNMP problems, see Diagnosing Simple Network Management Protocol (SNMP) problems. |
You can now perform the steps for the decision you have made.