PM63379: WITH SYSPLEXPORTS, BIND TO DRVIPA AND NON-ZERO LISTENING PORT ON A NON-DRVIPA OWNING STACK WILL NOT ACCEPT CONNECTION REQUESTS

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• In a sysplex distributor environment where SYSPLEXPORTS is coded
  on a VIPADISTRIBUTE statement and that a listener application
  is binding to a distributed DVIPA (DRVIPA) and a non-zero port
  on a target TCPIP stack that is not the DRVIPA owner, the
  listener will not accept a connection request to set up a
  passive secondary connection. For example, a client using
  Rational Developer for System z (RDz) will get the following
  error message from a RSED server that has _RSE_RSED_PORTRANGE
  environment variable configured for non-zero ports:
  
  RSEG1056 CONNECTION REFUSED.
           MAKE SURE THAT THE DATASTORE SERVER IS RUNNING ON
           host_name UNDER port port_number.
  

Local fix

• Do not allow the listener application to bind to DRVIPA and a
  non-zero port when using SYSPLEXPORTS on a target TCPIP stack
  that is not the DRVIPA owner. That is, use bind to a zero port
  so that the TCPIP stack will select an ephemeral port for the
  application. The listener application will then be able to set
  up a passive secondary connection using that port.
  
  KEYWORDS:
  DVIPA DRVIPA DISTRIBUTED SYSPLEXPORTS PORT PASSIVE
  RSEG1056 CONNECTION REFUSED DATASTORE RDZ RSED
  VIPADISTRIBUTE BIND EZBXFUTL EZBXFSRV _RSE_RSED_PORTRANGE
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of the IBM Communications Server   *
  *                 for z/OS Version 1 Release(s) 12 and 13      *
  *                 IP: SYSPLEXPORTS                             *
  ****************************************************************
  * PROBLEM DESCRIPTION: A connection to a listener bound to a   *
  *                      distributed DVIPA and sysplex port on   *
  *                      a target host will fail.                *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When an application binds and listens on a distributed DVIPA
  and sysplex port at a distributed DVIPA target host, a
  connection routing table entry is not created on the
  distributor host. Therefore connections to the listener will
  not be routed from the distributor to the target and will fail.
  +-------------------------------------------------------------+
  + Please check our Communications Server for OS/390 homepages +
  + for common networking tips and fixes.  The URL for these    +
  + homepages can be found in Informational APAR II11334.       +
  +-------------------------------------------------------------+
  

Problem conclusion

• EZBXFUTL and EZBX6UTL have been modified to create a connection
  routing table entry when a listen is done on a distributed
  DVIPA and sypslex port.
  
  * Cross Reference between External and Internal Names
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

  UK78754 UK78755

Modules/Macros

• EZBXFUTL EZBX6UTL
  

Fix information

• Fixed component name

  TCP/IP V3 MVS

• Fixed component ID

  5655HAL00

Applicable component levels

• R1C0 PSY UK78754

     UP12/07/28 P F207

• R1D0 PSY UK78755

     UP12/07/28 P F207

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.