A fix is available
APAR status
Closed as new function.
Error description
New Function
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: * * All users of the IBM Communications Server for z/OS Version * * 2 Releases 1 and 2: Dynamic VIPA * **************************************************************** * PROBLEM DESCRIPTION: * * New Function to enhance the return information on a failed * * ioctl() request for SIOCSVIPA/6 to create a Dynamic VIPA * * with affinity. The -a option of the moddvipa utility can be * * used to create a Dynamic VIPA with affinity as an * * alternative to programming the ioctl(). * **************************************************************** * RECOMMENDATION: * **************************************************************** The SIOCSVIPA/6 ioctl() processing does not distinguish between a retryable condition and a request that is invalid based on the current VIPADYNAMIC configuration. If the TCPIP stack has not processed the VIPADYNAMIC configuration or has not joined or left the sysplex, the ioctl() request to create a Dynamic VIPA will fail with EINVAL and JrDVIPANotInVIPARange. The requested Dynamic VIPA address may be defined correctly within the scope of a VIPARANGE definition after the VIPADYNAMIC configuration is processed. It would be more appropriate under these circumstances to return a retryable error.
Problem conclusion
The SIOCSVIPA/6 ioctl() create with affinity processing has been amended to return EAGAIN and JrDVIPAServicesNotActive when the TCPIP stack has not processed the VIPADYNAMIC configuration. This provides the information needed for programs issuing the ioctl() and users of the moddvipa utility with the -a option to identify a retryable condition.
Temporary fix
Comments
APAR Information
APAR number
PI55277
Reported component name
TCP/IP V3 MVS
Reported component ID
5655HAL00
Reported release
210
Status
CLOSED UR1
PE
NoPE
HIPER
NoHIPER
Special Attention
YesSpecatt / New Function / Xsystem
Submitted date
2016-01-12
Closed date
2016-07-08
Last modified date
2017-01-25
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI39258 UI39259
Modules/Macros
EZBXFDYN EZBXFUDV EZBIEVPA
Fix information
Fixed component name
TCP/IP V3 MVS
Fixed component ID
5655HAL00
Applicable component levels
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":"210","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":"210","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
25 January 2017