A fix is available
APAR status
Closed as program error.
Error description
Customer is running with CHECKCLIENTCONN 5,5. During this process an abend4C5 occurs due to an invalid hash table.
Local fix
Remove CHECKCLIENTCONN from the Telnet Server profile. Then issue an Obeyfile command to rebuild the profile.
Problem summary
**************************************************************** * USERS AFFECTED: All users of the IBM Communications Server * * for z/OS Version 1 Releases 12 IP: Telnet * * Services using CheckClientConn * **************************************************************** * PROBLEM DESCRIPTION: ABEND4C5 in EZBTTCCC when using * * CheckClientConn * **************************************************************** * RECOMMENDATION: * **************************************************************** The problem may be summarized as followed: 1. CheckClientConn is coded in the Telnet profile with small value specified for the maximum number of connections to be checked. 2. There are more connections using the same IP address than the value specified on CheckClientConn. 3. A new connection is established with the same IP address, thus driving the CheckClientConn logic to send timemarks. 4. The number of outstanding timemarks already exceeds the value specified on CheckClientConn, so no more are sent at this time. The ABEND4C5 in EZBTTCCC occurs when trying to free a reference, on a hash table, that was never obtained. +-------------------------------------------------------------+ + 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
EZBTTCCC is updated to issue the HashTab FindComp only if it has already issued the HashTab FindAll. Also, ConnToken is now cleared when HashTab FindComp is issued. Also, EZBTTCCC is updated to ensure that it does not send more timemarks, in one dispatch, than specified on CheckClientConn. * Cross Reference between External and Internal Names
Temporary fix
Comments
APAR Information
APAR number
PI08747
Reported component name
TCP/IP V3 MVS
Reported component ID
5655HAL00
Reported release
1C0
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2013-12-27
Closed date
2014-01-08
Last modified date
2014-03-03
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI14068
Modules/Macros
EZBTTCCC
Fix information
Fixed component name
TCP/IP V3 MVS
Fixed component ID
5655HAL00
Applicable component levels
R1C0 PSY UI14068
UP14/02/19 P F402
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":"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:
03 March 2014