PI44955: DVIPA FAILS TO RETURN TO THE STACK WHERE IT IS DEFINED

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• DVIPA fails to return to the stack where it is defined. The
  message issued is:
  EZZ8308I ip_addr NOT DEFINED - OWNED BY tcp_jobname ON mvsname
  The reason for the failure is that the backup stack who
  currently owns the VIPA is slow in sending out the DVIPA table.
  Thus, this table arrives the original stack when the DVIPA
  statements are already processed.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All users of the Communications Server for z/OS Version 2    *
  * Release 1 IP                                                 *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * DVIPA fails to return to the stack where it is defined when  *
  * it has been taken over by a backup stack.  The stack trying  *
  * to activate the DVIPA detects it is an active IP address but *
  * fails to detect it is an active DVIPA.  Message EZZ8308I is  *
  * issued and the activation fails.                             *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Apply PTF                                                    *
  ****************************************************************
  The activation of a DVIPA goes through a validation check to
  ensure the IP address is not already active in the sysplex.
  When the IP address is found to be active additional checking is
  done to determine if it represents a DVIPA.  The methods
  available to determine the status of the IP address present
  timing conditions that can lead to an invalid result.  This can
  cause the validation logic to determine the IP address is active
  in the sysplex as a non-DVIPA.  When this occurs the activation
  of the DVIPA fails to prevent the creating a duplicate IP
  address.  Message EZZ8308I ip_addr NOT DEFINED - OWNED BY
  tcp_jobname ON mvsname is issued.
  
  The DVIPA validation logic provides no protection in the reverse
  scenario, where a DVIPA is active and another stack activates
  the same IP address for a static VIPA or a home address for an
  interface.  The lack of validation in the reverse scenario and
  the timing conditions that can lead to an incorrect
  determination of the status of an IP address cannot be resolved
  under the current method of exchanging IP address information in
  the sysplex.  The DVIPA validation logic is being removed for
  other stacks in the sysplex, while retaining the test for a
  duplicate IP address owned by the activating stack.  The
  validation for a remote owner will still occur for a DVIPA that
  has been deactivated in the sysplex, which can result in the
  issuing of message EZZ8308I.
  

Problem conclusion

• The DVIPA validation logic has been amended to remove the check
  for remote system duplicate IP detection when the DVIPA has not
  been deactivated.
  

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:

  UI30440 UI30441

Modules/Macros

• EZBX6DVI EZBXFUDV EZBXFDVI
  

Fix information

• Fixed component name

  TCP/IP V3 MVS

• Fixed component ID

  5655HAL00

Applicable component levels

• R220 PSY UI30441

     UP15/10/29 P F510

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.