A fix is available
APAR status
Closed as program error.
Error description
For the Host client this variable act as an IDLETHREADTIMEOUT on LUW server. We have to have an option: connection never times out. This APAR introduces this option. Value of DB2_SERVER_CONTIMEOUT=0 will do this.
Local fix
Increase the value to the max of 32767.
Problem summary
Users affected: All Problem summary: Unexpected closing of the idle connection by the server side after 180 secs on the v8fp12 level and above. Problem summary: Connection closed on the server side after 180 secs of the idle time. 180 is a default value of the registry DB2_SERVER_CONTIMEOUT. This registry was introduced in fp12. This APAR allows to disable the influence of registry DB2_SERVER _CONTIMEOUT by setting it to 0 value => never timeout the idle connections by the server side.
Problem conclusion
First fixed in v8FP16, s080111
Temporary fix
Set the variable to the max value 32767 as a potential workaround
Comments
APAR Information
APAR number
LI72085
Reported component name
DB2UDB ESE LINU
Reported component ID
5765F4105
Reported release
820
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2007-03-08
Closed date
2008-02-13
Last modified date
2008-02-13
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
IZ07458
Fix information
Fixed component name
DB2UDB ESE LINU
Fixed component ID
5765F4105
Applicable component levels
R820 PSY
UP
[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSEPGG","label":"DB2 for Linux- UNIX and Windows"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"820","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
16 October 2021