A fix is available
APAR status
Closed as unreproducible.
Error description
The failing OSA adapter had to be manually stopped and restarted after a successfully ARP takeover. When TCPIP tried to register the VIPA or Dynamic VIPA with the OSA adapter it failed with the following message for both physical adapters: EZZ4309I ATTEMPTING TO RECOVER DEVICE GIGP0A EZZ4329I LINK GIG0C HAS TAKEN OVER ARP RESPONSIBILITY FOR INACTIVE LINK GIG0A EZZ4313I INITIALIZATION COMPLETE FOR DEVICE GIGP0A EZZ4327I ERROR E00A REGISTERING IP ADDRESS 10.169.60.22 FOR DEVICE GIGP0A EZZ4327I ERROR E00A REGISTERING IP ADDRESS 10.169.70.12 FOR DEVICE GIGP0A EZZ4327I ERROR E00A REGISTERING IP ADDRESS 10.169.70.13 FOR DEVICE GIGP0A EZZ4327I ERROR E00A REGISTERING IP ADDRESS 10.169.70.12 FOR DEVICE GIGP0C EZZ4327I ERROR E00A REGISTERING IP ADDRESS 10.169.70.13 FOR DEVICE GIGP0C
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of the IBM Communications Server * * for z/OS Version 1 Release 2 IP: * * iQDIO and OSA-E QDIO using Dynamic VIPA * **************************************************************** * PROBLEM DESCRIPTION: ERROR: EZZ4327I E00A REGISTERING IP * * ADDRESS seen during SETIP processing * * for iQDIO or OSA-E QDIO. Frequently * * associated with DVIPA takeover. * **************************************************************** * RECOMMENDATION: * **************************************************************** Timing windows exist within which SETIPs are issued in multiple locations for the same IP Address. This is usually associated with DVIPA takeover/takeback scenarios when the IP address has not yet been unregistered at the location giving up the address via a DELIP before the SETIP is issued. It can also occur when multiple devices are initializing and one does not know the IP Address is also being activated on a partner system. +-------------------------------------------------------------+ + 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
New bits will be added and checked to avoid the contention issues during IP Registration processing.
APAR Information
APAR number
PQ63068
Reported component name
TCP/IP V3 MVS
Reported component ID
5655HAL00
Reported release
120
Status
CLOSED UR3
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2002-07-11
Closed date
2002-08-27
Last modified date
2002-10-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UQ69358
Modules/Macros
EZBIFIND EZBIFIOC EZBIFIUM EZBIFIUT EZBIPEPR TOMPHYSI TONFINSI
Fix information
Fixed component name
TCP/IP V3 MVS
Fixed component ID
5655HAL00
Applicable component levels
R120 PSY UQ69358
UP02/09/25 P F209
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":"120","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":"120","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
02 October 2002