81 lines
6.2 KiB
HTML
81 lines
6.2 KiB
HTML
|
<?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 concepts" />
|
||
|
|
<meta name="abstract" content="This topic provides information to help you understand how commitment control works, how it interacts with your system, and how it interacts with other systems in your network." />
|
||
|
|
<meta name="description" content="This topic provides information to help you understand how commitment control works, how it interacts with your system, and how it interacts with other systems in your network." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakjcommitkickoff.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakjhowworks.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakjrollbacks.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakjcommitdef.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakjresources.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakjiasp.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakjmiscconsid.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakjcommitbatch.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakjtwophase.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakjxatransaction.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakjthreadscoped.htm" />
|
||
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 2004, 2006" />
|
||
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 2004, 2006" />
|
||
|
|
<meta name="DC.Format" content="XHTML" />
|
||
|
|
<meta name="DC.Identifier" content="rzakjconcepts" />
|
||
|
|
<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 concepts</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzakjconcepts"><a name="rzakjconcepts"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Commitment control concepts</h1>
|
||
|
|
<div><p>This topic provides information to help you understand how commitment
|
||
|
|
control works, how it interacts with your system, and how it interacts with
|
||
|
|
other systems in your network.</p>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<ul class="ullinks">
|
||
|
|
<li class="ulchildlink"><strong><a href="rzakjhowworks.htm">How commitment control works</a></strong><br />
|
||
|
|
Commitment control is a function that allows you to define and process a group of changes to resources, such as database files or tables, as a transaction.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzakjrollbacks.htm">How commit and rollback operations work</a></strong><br />
|
||
|
|
Commit and rollback operations affect changes that are made under commitment control.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzakjcommitdef.htm">Commitment definition</a></strong><br />
|
||
|
|
You create a commitment definition when you use the Start Commitment
|
||
|
|
Control (STRCMTCTL) command to start commitment control on your system. Also, DB2
|
||
|
|
Universal Database™ (UDB) for iSeries™ automatically creates a commitment
|
||
|
|
definition when the isolation level is other than No Commit.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzakjresources.htm">How commitment control works with objects</a></strong><br />
|
||
|
|
When you place an object under commitment control, it becomes a committable resource. It is registered with the commitment definition. It participates in each commit operation and rollback operation that occurs for that commitment definition.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzakjiasp.htm">Commitment control and independent disk pools</a></strong><br />
|
||
|
|
Independent disk pools and independent disk pool groups, can each
|
||
|
|
have a separate i5/OS™ SQL
|
||
|
|
database. You can use commitment control with these databases. </li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzakjmiscconsid.htm">Considerations and restrictions for commitment control</a></strong><br />
|
||
|
|
The topic talks about miscellaneous considerations and restrictions for commitment control.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzakjcommitbatch.htm">Commitment control for batch applications</a></strong><br />
|
||
|
|
Batch applications might or might not need commitment control. In some cases, a batch application can perform a single function of reading an input file and updating a master file. However, you can use commitment control for this type of application if it is important to start it again after an abnormal end.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzakjtwophase.htm">Two-phase commitment control</a></strong><br />
|
||
|
|
Two-phase commitment control ensures that committable resources on multiple systems remain synchronized.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzakjxatransaction.htm">XA transaction support for commitment control</a></strong><br />
|
||
|
|
DB2
|
||
|
|
Universal Database™ (UDB) for iSeries™ can participate in X/Open global
|
||
|
|
transactions. </li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzakjthreadscoped.htm">SQL server mode and thread-scoped transactions for commitment control</a></strong><br />
|
||
|
|
Commitment definitions with job-scoped locks are normally scoped to an activation group.</li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzakjcommitkickoff.htm" title="Commitment control is a function that ensures data integrity. It allows you to define and process a group of changes to resources, such as database files or tables, as a transaction.">Commitment control</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|