Enabling KEEPDYNAMIC refresh for DBATs
Db2 can use KEEPDYNAMIC refresh to seamlessly reroute database access threads (DBATs) for Db2 Connect applications that use packages that are bound with the KEEPDYNAMIC(YES) bind option.
About this task
With KEEPDYNAMIC refresh, when a timeout occurs for a DBAT that uses a package that is bound with KEEPDYAMIC(YES), it seamlessly routes to another DBAT for further processing, transparently to the application. If a DBAT uses a package that is bound with KEEPDYNAMIC(YES) and enabled with automatic client reroute, the thread is automatically terminated at a commit boundary during its processing in the following situations:
- The maximum use time exceeds 1 hour.
- The maximum idle wait time for the next transaction request exceeds 20 minutes.
Procedure
To enable KEEPDYNAMIC refresh for database access threads, use one of the following approaches to enable automatic client reroute in the data sharing group:
- Set up client affinities for the Db2 data sharing group. For more information, see .
- Use sysplex workload balancing. For more information, see Configuration of sysplex workload balancing and automatic client reroute for Java clients.
