DisableAutoCommit IBM data server driver configuration keyword
Disables the application's autocommit after each statement.
- Equivalent CLI keyword
- AutoCommit
- Equivalent IBM® Data Server Provider for .NET connection string keyword
- N/A
- db2dsdriver.cfg configuration syntax
<parameter name="DisableAutoCommit" value="0 | 1"/>- Default setting:
- Each statement is treated as a single, complete transaction.
- Equivalent connection attribute:
- SQL_ATTR_AUTOCOMMIT
- Usage notes:
- To be consistent with ODBC, CLI defaults with DisableAutoCommit on, which means each statement is treated as a single, complete transaction. This keyword can provide an alternative default, but will only be used if the application does not specify a value for SQL_ATTR_AUTOCOMMIT.
- 0 = SQL_ATTR_AUTOCOMMIT_ON (default)
- 1 = SQL_ATTR_AUTOCOMMIT_OFF
Note: Most ODBC applications assume the default of DisableAutoCommit to be on. Extreme care must be used when overriding this default during runtime as the application can depend on this default to operate properly.This keyword also allows you to specify whether autocommit should be enabled in a Distributed Unit of Work (DUOW) environment. If a connection is part of a coordinated Distributed Unit of Work, and DisableAutoCommit is not set, the default does not apply; implicit commits arising from autocommit processing are suppressed. If DisableAutoCommit is set to 0, and the connection is part of a coordinated Distributed Unit of Work, the implicit commits are processed. This can result in severe performance degradation, and possibly other unexpected results elsewhere in the DUOW system. However, some applications might not work at all unless this is enabled.
A thorough understanding of the transaction processing of an application is necessary, especially applications written by a third party, before applying it to a DUOW environment.