APAR status
Closed as fixed if next.
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
Make sure that the backup stack is not low in CPU resource.
Problem summary
**************************************************************** * USERS AFFECTED: All users of the IBM Communications Server * * for z/OS Version 1 Release(s) 12 and 13 IP: * * Dynamic VIPA * **************************************************************** * PROBLEM DESCRIPTION: Dynamic VIPA define fails with message * * EZZ8308I when the DVIPA is in backup * * status in the Sysplex. * **************************************************************** * RECOMMENDATION: * **************************************************************** Dynamic VIPA define fails with message EZZ8308I when the DVIPA is in backup status in the Sysplex. Members of the same Sysplex group or subgroup exchange a table of IP addresses they have defined that includes physical interfaces, static VIPAs, and dynamic VIPAs. They also exchange a table of just the dynamic VIPAs. During activation of a dynamic VIPA a check is performed to determine if the IP address is defined as a dynamic VIPA on another TCP/IP stack. If the IP address is not an active dynamic VIPA another check is done to see if the IP address is defined on another TCP/IP stack. If the IP address is not found to be a dynamic VIPA but is found to be a defined IP address the activation will fail with message EZZ8308I ip_addr NOT DEFINED - OWNED BY tcp_jobname ON mvsname. A timing window exists where the activation of a dynamic VIPA occurs after the table of IP addresses has been received from a member of the group but the dynamic VIPA table has not. The dynamic VIPA activation process does not find the IP address in any known dynamic VIPA table but does find it in an IP address table and fails the activation. +-------------------------------------------------------------+ + 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 F156091 by Communications Server for z/OS Development. The solution for this APAR is included in CS for zOS Version 2 Release 1 and 2 via PI44955.
APAR Information
APAR number
PM70274
Reported component name
TCP/IP V3 MVS
Reported component ID
5655HAL00
Reported release
1C0
Status
CLOSED FIN
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-08-03
Closed date
2012-09-07
Last modified date
2015-09-09
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
R1C0 PSY
UP
[{"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":"1C0","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":"1C0","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
09 September 2015