|
Problem IC67823
|
Status: Closed |
RECEIVE TIMEOUT IS RESET TO 0 WHEN BOTH OF DB2TCP_CLIENT_ RCVTIMEOUT AND DB2TCP_CLIENT_CONTIMEOUT ARE SET |
| product: |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 |
| Problem description: |
When only DB2TCP_CLIENT_RCVTIMEOUT registry is set, it works as
expected. However, when both of DB2TCP_CLIENT_RCVTIMEOUT and
DB2TCP_CLIENT_CONTIMEOUT are set, the receive timeout is not
detected at the specified time interval. Receive timeout is
reset to 0 in connect post processing. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Users setting both of DB2TCP_CLIENT_RCVTIMEOUT *
* andDB2TCP_CLIENT_CONTIMEOUT *
****************************************************************
* PROBLEM DESCRIPTION: *
* When both of DB2TCP_CLIENT_RCVTIMEOUT *
* andDB2TCP_CLIENT_CONTIMEOUT are set, the receive timeout is *
* notdetected at the specified time interval. *
****************************************************************
* RECOMMENDATION: *
**************************************************************** |
| Local Fix: |
Specify only DB2TCP_CLIENT_RCVTIMEOUT registry |
| available fix packs: |
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
The problem was first fixed in Version 9.5 FP6 |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC68179 IC68180
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 13.04.2010
14.05.2010
14.05.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.5.FP6
|
| Problem solved according to the fixlist(s) of the following version(s) |
