PM71727: DVIPA DEFINED IN THE VIPARANGE STATEMENT NOT CREATED WHEN THE BIND IS ISSUED.

APAR status

• Closed as fixed if next.

Error description

• The DVIPA defined in the VIPARANGE statement is not created when
  the BIND from an application is issued.  This would happen if
  the VIPARANGE statement is applied to the TCPIP profile with an
  Obeyfile right after the stack is initialized (EZB6473I) and
  before the stack joins the sysplex (EZD1176I).
  

Local fix

• Include the VIPARANGE definition in the TCPIP profile or apply
  the VIPARAGE definition to the profile after the stack joins the
  sysplex.
  

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 added using OBEYFILE during         *
  *                      initialization will fail.               *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The problem can be summarized as follows:
  1. TCPIP is initialized.
  2. An Obeyfile with a VIPARANGE is automatically executed upon
  display of message:
  EZAIN11I ALL TCPIP SERVICES FOR PROC procedure name ARE
  AVAILABLE
  3. An application BINDs to a DVIPA address in the DVIPA
  VIPARANGE.
  4. The BIND fails with Reason Code=744C7230
  Reason Code Description: Local address was not active
  when processing the bind request.
  
  A timing window exists when TCPIP initialization and OBEYFILE
  processing for a DVIPA are executed simultaneously. During this
  window DVIPA OBEYFILE 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 OBEYFILE.
  +-------------------------------------------------------------+
  + 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

Temporary fix

Comments

• This APAR is being closed FIN (Fixed If Next) with concurrence
  from the submitting customer. This means that a fix to this
  APAR is expected to be delivered from IBM in a release (if any)
  to be available within the next 24 months.
  
  This problem will be tracked as Feature F156104
  by Communications Server for z/OS Development.
  
  The solution for this APAR is included in z/OS
  Communications Server Version 1 Release 13 by
  the corrective fix for APAR PM75676.
  
  The solution for this APAR is included in
  CS for zOS Version 2 Release 1.
  

APAR Information

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

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

Fix information

Applicable component levels

• R1D0 PSY

     UP