Commitment control considerations

Run ODBC autocommit support to different commit levels.

Beginning with V5R3, the commitment control model for the iSeries™ server, allows you to run ODBC autocommit support to use other commit levels than just *NONE. Prior to V5R3, autocommit support always runs under the *NONE commit level and *NONE will continue to be the default.

By specifying something other than *NONE, you can run autocommit under a different commit 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 ....

There is a SQLDriverConnect keyword called TRUEAUTOCOMMIT which allows an application to control whether or not it run autocommit under the *NONE commit 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 commit level.