Fixes are available
APAR status
Closed as program error.
Error description
CLI computes large time differences when it receives incorrect results for "get_current_clock_ticks" type calls to the underlying OS on some platforms / firmware versions. This APAR introduces compensating logic in CLI to correct for these errors, thus closely preserving the CLI application's declared timeout requirements on SQL_ATTR_LOGIN_TIMEOUT and SQL_ATTR_QUERY_TIMEOUT.
Local fix
Set CONNECTTIMEOUT=0 in db2cli.ini. This will cause CLI to wait indefinitely for connections to complete, but will avoid the erroneous timeout described by this APAR.
Problem summary
User's affected: All that use CLI applications after migration to v9 release
Problem conclusion
First fixed in v9.1fp8
Temporary fix
set explicitly ConnectTimeout=0 in db2cli.ini file
Comments
APAR Information
APAR number
JR33307
Reported component name
DB2 CUE WINDOWS
Reported component ID
5724B6201
Reported release
910
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-06-10
Closed date
2009-10-06
Last modified date
2009-10-06
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
DB2 CUE WINDOWS
Fixed component ID
5724B6201
Applicable component levels
R910 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":"910","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
12 October 2021