High Availability Guide : Using HotStandby with applications : Defining timeouts between applications and servers : Application read timeout option
  
Application read timeout option
The application read timeout option helps detect failures in low level network RPC read operations. The timeout setting applies to the read in the physical network (TCP/IP protocol only).
This RPC read timeout (called connection timeout in ODBC and JDBC) can be configured (in milliseconds) in the following ways. The default timeout is 0 – infinite (operating system default timeout applies),
Client-side Com.ClientReadTimeout parameter
For example:
[Com]
;Set RPC read timeout to 1000 milliseconds (one second)
ClientReadTimeout=1000
Client-side Com.Connect parameter with option -rmilliseconds
For example:
[Com]
;Set RPC read timeout to 1000 milliseconds (one second)
Connect=TCP -r1000 1313
Note For client applications such as the watchdog, it is convenient to provide the RPC read timeout (called also connection timeout) in the Com.Connect parameter using the -r option. Otherwise certain network failure types may cause indefinite waits.
Note The Connect parameters in the [Com] section, [Watchdog] section, and [Hotstandby] section are for different purposes. Make sure that you edit the correct one.
Connect string of the SQLConnect function (-r option)
For example:
SQLConnect (hdbc, "TCP -r1000 1313", SQL_NTS,
"dba", SQL_NTS, "dba", SQL_NTS);
In the example above, the constant SQL_NTS indicates that the previous string (servername, username, or password) was passed as a standard Null-Terminated String.
See also
Defining timeouts between applications and servers