For details about the BES connection holding facility, see the HiRDB Version 8 System Operation Guide.
- 57) pd_bes_connection_hold = Y | N
- This operand is applicable only to a HiRDB/Parallel Server.
- Specifies whether to use the BES connection holding facility.
- Y: The BES connection holding facility is used.
- N: The BES connection holding facility is not used.
- Relationship to the client environment definition
- The value of this operand can be changed for each client. To change the operand for a client, specify the PDBESCONHOLD operand in the client environment definition. For details about the PDBESCONHOLD operand, see the HiRDB Version 8 UAP Development Guide.
- Note
- When you use the BES connection holding facility, make sure that the following condition is satisfied:
- number-of-processes-in-each-back-end-server (value of the pd_max_bes_process operand)
number-of-all-front-end-server-processes (value of the pd_max_users operand
number-of-front-end-servers) - If this condition is not satisfied, a shortage in the number of back-end server processes may cause an SQL error. Furthermore, if you plan to execute a program such as a utility while HiRDB is running, additionally, allocate the number of back-end server processes required by the utility.
- 58) pd_bes_conn_hold_trn_interval = back-end-server-connection-hold-time
<unsigned integer>((0-3600))<<1>>(seconds)- Specifies the BES connection holding period in seconds.
- When the BES connection holding facility is used, HiRDB monitors the period between the termination of a transaction and the execution of the next transaction. If this period is within the specified value, the connection between the front-end server and the back-end server is maintained. However, if this period exceeds the specified value, the connection between the front-end server and the back-end server is terminated after the transaction is terminated.
- If 0 is specified for this operand, the period is not monitored. The connection between the front-end server and the back-end server is terminated only when the connection between the front-end server and a client is terminated by SQL DISCONNECT (xa_close if the XA library is being used) or because the value of the PDCWAITTIME operand is exceeded.