ibm-information-center/dist/eclipse/plugins/i5OS.ic.rzaik_5.4.0.1/rzaikcommitcontrol.htm

55 lines
3.3 KiB
HTML
Raw Normal View History

2024-04-02 14:02:31 +00:00
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html lang="en-us" xml:lang="en-us">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<meta name="security" content="public" />
<meta name="Robots" content="index,follow" />
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
<meta name="DC.Type" content="concept" />
<meta name="DC.Title" content="Commitment control considerations" />
<meta name="abstract" content="Run ODBC autocommit support to different commit levels." />
<meta name="description" content="Run ODBC autocommit support to different commit levels." />
<meta name="DC.Relation" scheme="URI" content="rzaikodbcapifunctions.htm" />
<meta name="copyright" content="(C) Copyright IBM Corporation 1999, 2006" />
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 1999, 2006" />
<meta name="DC.Format" content="XHTML" />
<meta name="DC.Identifier" content="rzaikcommitcontrol" />
<meta name="DC.Language" content="en-us" />
<!-- All rights reserved. Licensed Materials Property of IBM -->
<!-- US Government Users Restricted Rights -->
<!-- Use, duplication or disclosure restricted by -->
<!-- GSA ADP Schedule Contract with IBM Corp. -->
<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
<link rel="stylesheet" type="text/css" href="./ic.css" />
<title>Commitment control considerations</title>
</head>
<body id="rzaikcommitcontrol"><a name="rzaikcommitcontrol"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">Commitment control considerations</h1>
<div><p>Run ODBC autocommit support to different commit levels.</p>
<p>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. </p>
<p>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 ....</p>
<p>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. </p>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaikodbcapifunctions.htm" title="Learn about implementations issues when using ODBC APIs.">Implementation issues of ODBC APIs</a></div>
</div>
</div>
</body>
</html>