A fix is available
APAR status
Closed as unreproducible.
Error description
If the count of IPv6 VIPAROUTEs is larger than the count of IPv4 VIPAROUTEs according to TCPIP profile, NETSTAT VIPADCFG/-F might result in no output at all for the display. The TCPIP stack has rejected the request from the NETSTAT command because the calculated buffer size was too small for the records containing the IPv4 and IPv6 DVIPA definitions in the TCPIP profile for the display. Adding the DEBUG/-Z option to the NETSTAT command will show errno 1122 (ENOBUFS) with errnojr 765A006B (JRBUFFTOOSMALL) in the NETSTAT debug report. Note: This problem is fixed in z/OS 1.11 (R1B0) base code.
Local fix
Remove the IPv6 VIPAROUTE definitions or ensure that the count of IPv4 VIPAROUTE definitions is the same as the one for IPv6 VIPAROUTE definitions (when allowed for the configuration). Note: This problem has been fixed in z/OS 1.11 (R1B0) base code. KEYWORDS: NETSTAT VIPADCFG VIPAROUTE 1122 ENOBUFS 765A006B JRBUFFTOOSMALL SIOCGDVIPACONF IOCTL EZACDNE1 IPV6 EZBIEGVC EZBIEVPA EZBXFGCF EZBXFIOC
Problem summary
**************************************************************** * USERS AFFECTED: All users of the IBM Communications Server * * for z/OS Version 1 Release 10 IP: * * VIPAROUTE * **************************************************************** * PROBLEM DESCRIPTION: NETSTAT VIPADCFG/-F fails to display * * any output. The TCP/IP profile must * * have VIPAROUTE configured with an IPv6 * * address. Adding the DEBUG/-Z parameter * * to the NETSTAT command will show the * * failure message: * * netIoctl(): IOCTL process failed with * * rtnValue -1, rtnCode 1122, * * and rsnCode 765A006B * **************************************************************** * RECOMMENDATION: * **************************************************************** NETSTAT VIPADCFG/-F fails to display any output. The TCP/IP profile must have VIPAROUTE configured with an IPv6 address. Adding the DEBUG/-Z parameter to the NETSTAT command will show the failure message: netIoctl(): IOCTL process failed with rtnValue -1, rtnCode 1122, and rsnCode 765A006B The error only occurs when the number of VIPAROUTE statements with IPv6 addresses exceeds the VIPAROUTE statements with IPv4 addresses. The routine that collects the dynamic VIPA configuration information operates in a two pass model. The first pass calculates the number of buffer entries required to display the configuration and verifies the NETSTAT supplied buffer is large enough. The second phase moves the configuration data into the supplied buffer if the first phase determined there was enough buffer space. The number of IPv6 VIPAROUTEs is added to the total entry count correctly during the first phase, however the number of IPv4 VIPAROUTEs is incorrectly saved in a local variable as the number of IPv6 VIPAROUTEs. During the second phase, a test is done to ensure the number of IPv6 VIPAROUTEs is not higher than the number used to validate the size of the input buffer. If the current number of IPv6 VIPAROUTEs is larger than the saved value (IPv4 VIPAROUTEs), an ENOBUFS error is returned. The first phase should be saving the number of IPv6 VIPAROUTEs to use for the comparison in the second phase. +-------------------------------------------------------------+ + 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
EZBXFIOC has been amended to save the number of IPv6 VIPAROUTEs used in the buffer size calculation. The comparison of the current number of IPv6 VIPAROUTEs to the saved number of IPv6 VIPAROUTEs will not generate an ENOBUFS error condition unless new IPv6 VIPAROUTEs are added while the NETSTAT command is executing.
APAR Information
APAR number
PM24124
Reported component name
TCP/IP V3 MVS
Reported component ID
5655HAL00
Reported release
1A0
Status
CLOSED UR3
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2010-10-07
Closed date
2010-10-29
Last modified date
2011-01-03
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK61823
Modules/Macros
EZBXFIOC
Fix information
Fixed component name
TCP/IP V3 MVS
Fixed component ID
5655HAL00
Applicable component levels
R1A0 PSY UK61823
UP10/12/15 P F012
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":"1A0","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":"1A0","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
03 January 2011