If lan_operation is CLOSE_STATION_INDICATION, action is RECEIVED, and return_code is *NA*, VTAM has been informed that the station, previously opened or in the process of being opened, has closed.

APPN CONNECTION ENDED BY ACTIVATION XID

An effort to activate a new APPN connection has been received over an already active connection. The existing APPN connection and ATM SVC or PVC will be terminated and automatically restarted. When the new APPN connection attempt is tried again, the SVC or PVC should be re-established.

APPN CONNECTION ENDED DUE TO INACTIVITY

No HPR traffic has been detected for the DISCNT time period specified on the PU statement representing this connection. The ATM switched virtual circuit (SVC) will be terminated. This is a normal condition when session traffic has ceased to use this connection. The next session request will cause activation of another ATM SVC.

APPN CONNECTION FAILED – LIVENESS TIMEOUT

An APPN connection is being terminated over an ATM PVC because the remote end of the PVC is not responding to liveness messages. The PVC and the APPN connection over it will be terminated and automatically restarted. If no response is then received, the APPN connection will remain open pending activation of the PVC from the remote node.

APPN CONNECTION FAILED – STORAGE FAILURE

During APPN connection establishment, either an XID or an LDLC COMMAND could not be transmitted to the remote node because no storage was available. The APPN connection and the ATM SVC or PVC will be terminated. When the storage failure condition is relieved, this connection can be tried again.

EE HEALTH VERIFICATION FAILURE

Issue D NET,EEDIAG,ID=resourcename,TEST=YES to test the EE connection. See the information about understanding the EE connectivity test output in z/OS Communications Server: SNA Diagnosis Vol 1, Techniques and Procedures to interpret the output from the EEDIAG command.

INBOUND PIU COULD NOT BE ROUTED

• An ABEND occurred while processing the PIU. See IST1037I for recommended actions.
• A PIU was received out of sequence.

  The TG sequence number in the FID4 TH of the inbound PIU did not match the next sequence number that VTAM expected to receive. If VTAM internal trace was running, then PIU discard trace entries were written. Look for a DSCD entry that contains discard reason code 0001 and a module ID in the DSC2 trace record of LS6I. See z/OS Communications Server: SNA Diagnosis Vol 1, Techniques and Procedures for the format and content of the DSCD and DSC2 trace entries.

• A PIU was lost.

  A segment was received that did not complete a PIU before the start of a new PIU. If VTAM internal trace was running, then PIU discard trace entries were written. Look for DSCD entries that contain discard reason codes 0001 and 0004 and the module ID in the trace record of LS6Z. See z/OS Communications Server: SNA Diagnosis Vol 1, Techniques and Procedures for the format and content of the DSCD trace entry.

• The segment size was too large.

  An inbound PIU was received and the segment size exceeded the maximum frame size and the maximum PIU size. The maximum segment size for inbound PIUs is determined by the maximum PIU or frame size passed in the XID. If VTAM internal trace was running, then PIU discard trace entries were written. Look for DSCD entries that contain discard reason codes 0003 and 0004 and a module ID in the DSC2 trace record of LS6Z. See z/OS Communications Server: SNA Diagnosis Vol 1, Techniques and Procedures for the format and content of the DSCD and DSC2 trace entries.

• The PIU was not valid.

  If the INOPDUMP start option is ON, then an SVC DUMP was attempted by ISTTSCPD, whose name will appear in the title of the dump. Use the system log and dump to assist you in determining the reason for the INOP. See z/OS Communications Server: SNA Resource Definition Reference for more information on the INOPDUMP start option. If VTAM internal trace was running, then PIU discard trace entries were written. Look for a DSCD entry that contains discard reason code 0002 and a module ID in the DSC2 trace record of LS6I. See z/OS Communications Server: SNA Diagnosis Vol 1, Techniques and Procedures for the format and content of the DSCD and DSC2 trace entries.

LDLC COMMAND ERROR

The XID Done LDLC command establishing the primary end of the connection was received before XID negotiation completed. The remote node did not properly complete XID negotiation.

MACADDR OR SAPADDR IN USE

Verify that the MACADDR and SAPADDR for this connection is a unique pair. See z/OS Communications Server: SNA Resource Definition Reference for additional information on specifying MACADDR and SAPADDR in the XCA major node.

TCP/IP JOB jobname IS NOT AVAILABLE

The Enterprise Extender (HPR/IP) connection to TCP/IP was established, but due to a change in the TCP/IP job to which VTAM was attached, the connection cannot continue. The TCP/IP job name can be supplied to VTAM using the VTAM start option TCPNAME, which is modifiable using the MODIFY VTAMOPTS command. If the Enterprise Extender is active, a change in the TCPNAME value will not be detected. The TCPNAME value is used only when the Enterprise Extender is started. If the TCPNAME option is not used, the Enterprise Extender selects any TCP/IP job that is active.

TIMEOUT OCCURRED – PORT TIMER EXPIRED

Verify that the TIMER value on the PORT definition statement is high enough. See z/OS Communications Server: SNA Resource Definition Reference for additional information.

UNRECOGNIZED OPERATION

The reason for the INOP could not be determined. Contact the IBM support center.

XID ERROR

Either a non format 3 XID or an XID with an appended Control Vector 22 was received. If VTAM internal trace was running with the LCS option, then an LCSX trace entry will contain the XID in error sent from the remote end of the connection. The format of the XID or control vector 22 can be used to determine what part of the XID is not valid.

XID OR LDLC COMMAND TIMEOUT

During APPN connection establishment, either an XID or an LDLC COMMAND was sent to the remote node. No response was received. The XID or LDLC command was retransmitted multiple times without response.

ATM: The SVC or PVC is still active, but the remote node is not responding. The ATM SVC or PVC will be cleared to attempt to reset the error condition on the remote node.

Enterprise Extender (HPR\IP): Try the connection again by reissuing the dial. If failure persists, determine if the failure is a result of a system definition error or a network error. If the failure is a result of a system definition error, correct the error. If the failure is a result of a network error, contact the IP network provider.