A fix is available
APAR status
Closed as program error.
Error description
Given a GLOBALCONFIG EXPLICITBINDPORTRANGE definition with a range of ports in a TCPIP profile (for example, start at port 40000 for 5000 ports), the number of ports from a pool of ports unique across the sysplex keeps increasing unexpectedly with the following error message issued periodically: EZD1296I EXPLICITBINDPORTRANGE exhausted The number of ports required is determined from the display of the EZBEPORT structure from the following command: DISPLAY vtam_proc,STATS,TYPE=CFS,STRNAME=EZBEPORT,LIST=ALL Because of an expected growth in the EZBEPORT structure, an OBEYFILE command to increase EXPLICITBINDPORTRANGE had to be issued for temporary relief. For example, from range 40000-44999 to 40000-45999. But when the ports become exhausted again, the OBEYFILE command with a larger port range had to be reissued. A SYSTCPIP CTRACE with OPTIONS(XCF,TCPMIN) from the sysplex members might reveal exception records that indicate that the condition should not have occurred. For example: ---------------------------------------------------------------- SYSx XCF 00090305 10:37:28.427943 !HS3 RetEphem EBPR Usecnt Prob SYSx XCF 00090305 10:37:36.126423 !HS3 RetEphem EBPR Usecnt Prob ---------------------------------------------------------------- Details on these CTRACE records lead to a non-zero return code of 4 to indicate that a port will not be returned to the pool. For example, CTRACE records might show: ---------------------------------------------------------------- SYSx XCF 00090308 10:37:28.427943 HS3 Ret_EphemPort_EBPR exit HASID..0066 PASID..0066 SASID..0066 USER...TCPIP TCB....00000000 MODID..EZBXFUT6 REG14..2B23D4C4 DUCB...7E000C4C CID....00000000 PORT...0 CPUA...02 IPADDR. 0.0.0.0 ADDR...00000000 00000000_22E789E0 LEN....000004 return code +0000 00000004 ADDR...00000000 00000000_22E78BF9 LEN....000004 footprint +0000 00000000 ---------------------------------------------------------------- SYSx XCF 00090305 10:37:36.126423 !HS3 RetEphem EBPR Usecnt Prob HASID..0066 PASID..0066 SASID..0066 USER...TCPIP TCB....00000000 MODID..EZBXFUT6 REG14..2B23D3AA DUCB...70000C13 CID....00000000 PORT...0 CPUA...06 IPADDR. 0.0.0.0 ADDR...00000000 00000000_22DCDA50 LEN....000004 XEPH table ptr +0000 2D2C43B8 ADDR...00000000 00000000_2D2C43B8 LEN....000018 port table hdr +0000 C5D7C8C5 D4E3C2D3 00000000 10482B39 00370000 000A0040 ADDR...00000000 00000000_2D0003C8 LEN....000002 port returned +0000 9B31 ---------------------------------------------------------------- SYSx XCF 00090308 10:37:36.126424 HS3 Ret_EphemPort_EBPR exit HASID..0066 PASID..0066 SASID..0066 USER...TCPIP TCB....00000000 MODID..EZBXFUT6 REG14..2B23D4C4 DUCB...70000C13 CID....00000000 PORT...0 CPUA...06 IPADDR. 0.0.0.0 ADDR...00000000 00000000_22DCD9E0 LEN....000004 return code +0000 00000004 ADDR...00000000 00000000_22DCDBF9 LEN....000004 footprint +0000 00000000 ---------------------------------------------------------------- Because of this "should not occur" condition, the freed ports were not returned to the pool for the sysplex.
Local fix
Increase EXPLICITBINDPORTRANGE and issue VARY TCPIP,,OBEYFILE to update the port range dynamically. Repeat as necessary for temporary relief. KEYWORDS: EZD1296I GLOBALCONFIG EXPLICITBINDPORTRANGE EBPR XCF SYSPLEX EZBXFUT6 EZBEPORT PORT BIND PORTRANGE CFS HS3 USECNT
Problem summary
**************************************************************** * USERS AFFECTED: All users of the IBM Communications Server * * for z/OS Version 1 Release(s) 13 IP: * * EXPLICITBINDPORTRANGE * **************************************************************** * PROBLEM DESCRIPTION: EXPLICITBINDPORTRANGE ports not being * * returned to the coupling facility. * * Message EZD1296I will be issued when * * all the ports are exhausted. * **************************************************************** * RECOMMENDATION: * **************************************************************** EXPLICITBINDPORTRANGE ports are not returned to the coupling facility. Eventually this will exhaust the range of ports defined, causing message EZD1296I to be issued. The issue is caused by ports being returned twice, causing the use counts to get corrupted. This will cause other ports to not be returned. +-------------------------------------------------------------+ + 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
The EXPLICITBINDPORTRANGE free routine is updated to turn off the bit indicating a port is in use from the coupling facility. * Cross Reference between External and Internal Names
Temporary fix
Comments
APAR Information
APAR number
PI06006
Reported component name
TCP/IP V3 MVS
Reported component ID
5655HAL00
Reported release
1D0
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2013-11-12
Closed date
2013-12-03
Last modified date
2014-02-05
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI13147 PI07430
Modules/Macros
EZBXFUT2
Fix information
Fixed component name
TCP/IP V3 MVS
Fixed component ID
5655HAL00
Applicable component levels
R1D0 PSY UI13147
UP14/01/14 P F401
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":"1D0","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":"1D0","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
05 February 2014