A fix is available
APAR status
Closed as program error.
Error description
IWQ data traffic is forwarded to an incorrect stack when the OSA card is shared between the sysplex distributor stack and the target stack.
Local fix
There are several workarounds for this problem: 1. Disable IQDIO inbound workload queueing 2. Take out the VIPAROUTE statement so that distributed traffic will be sent to the target stack via XCF link instead of the shared OSA
Problem summary
**************************************************************** * USERS AFFECTED: * * All users of the IBM Communications Server * * for z/OS Version 2 Release 1 IP: * * QDIO Inbound Workload Queueing (IWQ) * * for sysplex distributor (SD) * **************************************************************** * PROBLEM DESCRIPTION: * * TCP connection hangs after bulk data * * detected. * **************************************************************** * RECOMMENDATION: * * Apply PTF. * **************************************************************** An OSA card is shared between two TCPIP stacks. One of the stacks is the distributor for a DVIPA and the other stack is a target for the DVIPA. The OSA is configured with QDIO Inbound Workload Queueing(IWQ) on both TCPIP stacks. A TCP connection is distributed to the target stack. TCPIP detects the connection is operating in bulk-data fashion and the connection is registered with the OSA. Future inbound packets are sent directly to the target. The target does not accept packets for distributed DVIPAs except from the distributor. The packet is forwarded to the distributor, but the OSA redirects the packet to the target stack again. This causes a loop forwarding the packet and the TCP connection hangs.
Problem conclusion
TCPIP is updated to accept packets for a DVIPA when the connection is established and in the dynamic VIPA connection routing table.
Temporary fix
Comments
APAR Information
APAR number
PI07587
Reported component name
TCP/IP V3 MVS
Reported component ID
5655HAL00
Reported release
210
Status
CLOSED PER
PE
NoPE
HIPER
YesHIPER
Special Attention
NoSpecatt
Submitted date
2013-12-06
Closed date
2013-12-23
Last modified date
2014-07-22
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI13809
Modules/Macros
EZB6PINB EZBX6UT3 EZBXFUT3 EZBIPINB EZB2IUDR
Fix information
Fixed component name
TCP/IP V3 MVS
Fixed component ID
5655HAL00
Applicable component levels
R210 PSY UI13809
UP14/03/04 P F403
Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.
[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"210","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SSCY4DZ","label":"DO NOT USE"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"210","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
22 July 2014