IST2117I
STALL CONTINUES FOR XCF TRLE trlename TO cpname

Explanation

This unsolicited message is issued at 60-second intervals as long as data flow continues to be stalled for an XCF connection. The stall was originally reported in an IST2116I message. The data flow is considered stalled because this node sent a pacing request to the partner node and a response has not been received. This might be an indication of an unresponsive partner or an internal software problem.

trlename is the name of the XCF TRLE.

cpname is the CP name of the partner node for this XCF connection.

System action

All outbound data flow across this XCF connection is suspended until the stall is alleviated. If the stall persists, this message is issued every 60 seconds until the stall is alleviated. If the pacing response is received from the partner node, the stall is considered alleviated and message IST2118I is issued.

When more than 15 minutes has elapsed since a pacing request was transmitted to the partner node, the XCF connection will be ended. When the connection is ended, message IST1578I is issued to indicate that an inoperative condition was detected. VTAM® automatically attempts to re-establish connectivity to the XCF partner.

Operator response

If the XCF data flow stall persists, VTAM or CSM storage might increase. To alleviate the storage problem, deactivate all of the users of this XCF connection by performing the following actions:

  1. Locate users of the device by issuing the D NET,ID=trlename command to obtain a list of the upper-layer protocols (ulp_id) using the XCF facility. Obtain the ulp_id from message IST1717I in the display output.
    • If VTAM is using this XCF TRLE for SNA traffic, the ulp_id represents SNA XCF PU name.
    • If TCP/IP is using the XCF TRLE for IP traffic, the ulp_id represents the TCP/IP job name.
  2. Deactivate the device for SNA traffic by issuing the V NET,INACT,ID=ulp_id,TYPE=FORCE command.
  3. Deactivate the device for IP traffic by performing the following steps on each TCP/IP stack that uses this device:
    • For predefined and dynamic IPv4 XCF connections, issue the V TCPIP,ulp_id,STOP,cpname command.
    • For predefined IPv6 XCF connections, issue the V TCPIP,ulp_id,STOP,intf_name command where intf_name is the user defined INTERFACE name for the IPv6 XCF connection. If the intf_name is not known, issue the D TCPIP,ulp_id,NETSTAT,DEVLINKS command. Locate the "DEVNAME: cpname" line of output. If found, locate the associated "INTFNAME: intf_name" line in the output, which follows the DEVNAME line.
    • For dynamic IPv6 XCF connections, issue the V TCPIP,ulp_id,STOP,EZ6XCFnn command where nn is the value of the MVS™ system symbol (SYSCLONE) of the partner node for this XCF connection.

System programmer response

First, investigate if the partner node is overloaded or involved in activity that will prevent it from responding. If XCF data flow stalls are prevalent and persistent, take a dump of both nodes at the next occurrence, then contact the IBM® software support center.

Source

z/OS® Communications Server SNA

Module

You can display the module that issues a SNA message in the message by setting the MSGMOD start option to YES. See Adding the originating module to the message text for more information about the MSGMOD start option.

Routing code

2

Descriptor code

4

Parent topic: IST messages for VTAM network operators IST2000I – IST2417I