There are three DSI configuration parameters that need to considered for each connection that will be batching commands:
batch
batch_begin
use_batch_markers
The following sections describe the configuration for the data servers and databases.
For these three data servers, use the following configuration:
batch = on
batch_begin = on or off
The use of on reduces the number of network transfers.
use_batch_markers = off
Additional batch markers are not required for these data servers.
For these two databases, use the following configuration:
batch = on
batch_begin = off
DB2 and UDB use the re_begin function string for a setup command to DirectConnect that cannot be batched.
use_batch_markers = on
For Informix data servers, use the following configuration:
batch = on
batch_begin = off
(It may be possible for the “BEGIN WORK” statement in Informix to be batched.
use_batch_markers = off
Additional batch markers are not required for Informix data servers.
For Oracle data servers, use the following configuration:
batch = on
batch_begin = off
As a result of a placeholder command that is used in the rs_begin function string, setting batch_begin to on can cause problems with starting DSI correctly. By setting batch_begin to off allows the rs_begin and the rs_commit commands to be sent independently of the batches of commands and insures correct SQL in all the commands being transferred.
use_batch_markers = on
Oracle requires a BEGIN and END to mark batches of commands that are not required for commands being sent individually. By configuring use_batch_markers to on, these are added from the rs_batch_start and rs_batch_end function strings.
