Lower values cause more frequent checks. As a guide, for low frequency, use 100; for medium frequency, use 50; for high frequency use 10. The value is measured in an internal DB2® metric. The values represent a linear scale, that is, increasing the value from 50 to 100 doubles the interval. Checking more frequently for client status while executing a database request lengthens the time taken to complete queries. If the DB2 workload is heavy (that is, it involves many internal requests), setting DB2CHECKCLIENTINTERVAL to a low value has a greater impact on performance than in a situation where the workload is light.
db2set
DB2_PMODEL_SETTINGS=MLN_REMOTE_LISTENER:TRUE;ENHANCED_ROLLBACK:TRUE
If you set this option to TRUE, ensure that the additional TCP/IP listeners do not use ports that are required by other services.
For detailed instructions on setting the DB2RSHCMD registry variable to use a ssh shell with DB2, see the white paper "Configure DB2 Universal Database™ for UNIX to use OpenSSH."
There is no timeout if the registry variable is not set or is set to 0.
The DB2TCP_CLIENT_KEEPALIVE_TIMEOUT registry variable specifies the maximum time in seconds before an unresponsive TCP/IP client connection or attachment is detected as no longer alive. When this variable is not set, the default setting of 15 seconds is used. When the KeepAliveTimeout keyword is set to 0, the keepalive setting that is set in the operating system takes effect. If set, this variable takes precedence over any keepAliveTimeout setting as specified in the db2dsdriver.cfg file.
Changes to this variable take effect immediately for all future TCP/IP connections and attachments to the server
There is no timeout if the registry variable is not set or is set to 0.