Isolation level considerations

Run IBM® i Access ODBC autocommit support to different isolation (commit) levels.

IBM i allows you to run ODBC autocommit support to use other isolation levels than just *NONE.

By specifying an isolation level something other than *NONE, you can run autocommit under a different isolation level. Be aware that an autocommit commitment levels other than *NONE require that you make additional other changes and that it changes the behavior of some functions, like eliminating the ability to update non-journaled files. For more information, see the Isolation level topic in the SQL Reference.

There is a SQLDriverConnect keyword called TRUEAUTOCOMMIT which allows an application to control whether or not it run autocommit under the *NONE isolation level or the SQL_ATTR_TXN_ISOLATION setting. If TRUEAUTOCOMMIT is set to 1 in the SQLDriverConnect connection string then the application will run autocommit using the SQL_ATTR_TXN_ISOLATION setting. If TRUEAUTOCOMMIT is not set, the default value of 0 is used. The default behavior will run autocommit using the *NONE isolation level.