MX 2.x)

When a command in the batch fails, the remaining commands of the batch are not executed resulting in re-execution

of entire batch. But, with this Batch Update Exception handling support, the remaining elements of the batch after the

error prone statement can be executed and hence re-execution of the entire batch jobs can be avoided.

contBatchOnError property

The contBatchOnError property communicates with JDBC driver to continue the remaining jobs in the batch even

after any BatchUpdateExceptions. This java property can be set from the command line as:

Djdbcmx.contBatchOnError={ON|OFF}

where

continues batch execution even after any other batch exception

OFF

terminates the batch execution on any other batch exception. The default is set to OFF.

Note: This property can be set either through java command line option or through property file of Datasource.

Statement Level Atomicity

To maintain the database consistency, transactions must be controlled so that they either complete successfully or are

aborted. With the prior release versions of JDBC/MX (before H10 AAB and V32 AAU on G-series), the transaction is

automatically aborted on any error while performing an SQL statement.

This version of JDBC/MX driver follows up with the SQL/MX 2.0 Statement Atomicity feature and guarantees that an

individual SQL statement within a transaction either completes successfully or has no effect on the database. When

this statement level atomicity is followed, with the auto commit mode set to false, any failure occurred during the

Insert, Update, or Delete operations will not abort the current transaction and this helps in execution of all the

statements under this current transaction until a commit or rollback is issued. This feature is optional and can be

enabled by setting the system property ‘stmtatomicity’.

stmtatomicity property

Enabling the stmtatomicity property, allows the JDBC driver to set the transactions atomicity at statement level.

This java property can be set from the command line as:

Djdbcmx.stmtatomicity={ON|OFF}

where

statement level atomicity

OFF

transaction level atomicity. The default is set to OFF.

Note: This functionality is already available in JDBC/MX H10AAB and V32AAU versions.

Managing Nonblocking JDBC/MX

Blocking mode with the JDBC/MX driver causes the whole JVM process to be blocked when an SQL operation