PM75676: DVIPA CREATE FAILS FOR VIPARANGE STATEMENT IN TCPIP PROFILE WHEN NODYNAMICXCF IS CONFIGURED.

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• When NODYNAMICXCF is configured, a DVIPA defined in the
  VIPARANGE statement in the TCPIP profile is not created when
  the BIND from an application is issued.
  
  Additional Symptom(s):
  
   - TSDX_InitDynCfgDone bit is not on
  
   - EZYFT13E bind error : EDC8116I Address not available.
                            (errno2=0x744C7230)
  
   - Use of the DVIPA Create IOCTL (SIOCSVIPA) will fail with
     errno 121 (EINVAL) reason 00007303 (JRDVIPANOTINVIPARANGE),
     even though the address is within a VIPARANGE and DYNAMICXCF
     is configured.
  

Local fix

• Use vipadefine to create the DVIPA address with obeyfile or
  recycle TCPIP
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of the IBM Communications Server   *
  *                 for z/OS Version 1 Release 13 IP:            *
  *                 DVIPA                                        *
  ****************************************************************
  * PROBLEM DESCRIPTION: BINDs to VIPARANGE DVIPA addresses that *
  *                      are defined in the TCP profile along    *
  *                      with NODYNAMICXCF may fail with         *
  *                      errno 744C7230.                         *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  1. TCPIP is initialized with a profile containing
     VIPARANGE and NODYNAMICXCF.
  2. An application BINDs to a DVIPA address in the DVIPA
     VIPARANGE.
  3. The BIND fails with Reason Code=744C7230
     Reason Code Description: Local address was not active
     when processing the bind request.
  
  A timing window exists during TCPIP initialization when
  both VIPARANGE and NODYNAMICXCF are defined. During this
  window VIPARANGE processing does not complete. This will
  result in a failure during a subsequent BIND to the DVIPA.
  This may also prevent AUTOLOG processing that was dependent on
  the completion of the DVIPA processing from completing.
  +-------------------------------------------------------------+
  + 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

• TCPIP was modified to correctly process a profile with
  both VIPARANGE and NODYNAMICXCF.
  
  * 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:

  UK83644

Modules/Macros

• EZBXFDYN
  

Fix information

• Fixed component name

  TCP/IP V3 MVS

• Fixed component ID

  5655HAL00

Applicable component levels

• R1D0 PSY UK83644

     UP13/01/25 P F301

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.