2.2.2 Operands related to application program status monitoring
- • adb_clt_rpc_con_wait_time =wait-time-until-completion-of-connection-to-HADB-server
-
~<integer>((1 to 300))<<300>> (seconds)
Specify the maximum amount of time (in seconds) to wait for HADB server connection processing to be completed. If HADB server connection processing is not completed within the specified amount of time, the connection processing is canceled and control is returned to the application program with an error.
Normally, there is no need to specify this operand. Specify this operand to reduce the timeout time if it takes a long time to establish a connection when the HADB server is busy.
- ■ When adb_clt_rpc_con_wait_time is specified in the JDBC driver properties
-
You can specify 0 in the adb_clt_rpc_con_wait_time operand in the JDBC driver properties. If you specify 0, the default value applies.
- • adb_clt_rpc_sql_wait_time =HADB-server's-response-wait-time
-
~<integer>((0 to 65,535))<<0>> (seconds)
Specify the maximum amount of time (in seconds) to wait for a response after a processing request has been issued from the HADB client to the HADB server. If there is no response from the HADB server within the specified time, a timeout error whose SQLCODE is -732 (KFAA30732-E) is returned to the application. When this occurs, processing of the SQL statement is canceled, and the transaction is rolled back. Then, the application is disconnected from the HADB server.
Note that depending on factors such as the timing with which the processing request was canceled and the nature of the communication error, there are situations in which the transaction might not be rolled back. If this occurs, we recommend that you check the result by viewing relevant information such as the messages output to the message log of the HADB server.
Specify this operand if you monitor SQL statements that require a long processing time. To determine an appropriate wait time to be specified in this operand, see 4.5 Handling unresponsive application programs.
If this operand is omitted or 0 is specified, no wait time is set.
- ■ When adb_clt_rpc_sql_wait_time is specified in the JDBC driver properties
-
When adb_clt_rpc_sql_wait_time is specified in the JDBC driver properties, HADB also monitors the following wait times:
-
When multiple SELECT statements are executed concurrently in the same connection, the wait time for processing real thread allocation when there are insufficient processing real threads
If this wait time is exceeded, HADB returns a timeout error whose SQLCODE is -1071570 (KFAA71570-E) to the application. When this happens, processing of the SQL statement is canceled but the transaction is not rolled back. Nor is the application disconnected from the HADB server.
For details about the purpose of specifying adb_clt_rpc_sql_wait_time, see (4) Note about executing multiple SELECT statements concurrently in the same connection in 7.4.1 How to retrieve data.
-
- • adb_clt_ap_name =application-identifier
-
~<character string>((1 to 30 bytes))<<********>>
Specify the identification information (application identifier) for the application program that is to be connected to the HADB server.
The application identifier you specify is displayed in the output of the command that displays connection statuses (adbls -d cnct), in messages, and in SQL trace information. This information is required in order to determine which application program is running.
Because application identifiers are recognized on the basis of the specification of the ADBCLTLANG environment variable, we recommend that you use a name consisting of only alphanumeric characters that do not depend on the character encoding.