74 lines
5.3 KiB
HTML
74 lines
5.3 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="Ensure data integrity with commitment control" />
|
||
|
|
<meta name="abstract" content="Commitment control lets you define and process a number of changes to database files in a single unit (transaction). It can ensure that complex application transactions are logically synchronized, even if the job or system ends. Two-phase commitment control ensures that committable resources, such as database files on multiple systems, remain synchronized." />
|
||
|
|
<meta name="description" content="Commitment control lets you define and process a number of changes to database files in a single unit (transaction). It can ensure that complex application transactions are logically synchronized, even if the job or system ends. Two-phase commitment control ensures that committable resources, such as database files on multiple systems, remain synchronized." />
|
||
|
|
<meta name="DC.subject" content="commitment control, journaling, referential constraints" />
|
||
|
|
<meta name="keywords" content="commitment control, journaling, referential constraints" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbaforzahfprd.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbafocctrans.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbafoccben.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbafoccusg.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../sqlp/rbafydicomm.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../db2/rbafzmstc4comit.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../db2/rbafzmstrollbac.htm" />
|
||
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 1998, 2006" />
|
||
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 1998, 2006" />
|
||
|
|
<meta name="DC.Format" content="XHTML" />
|
||
|
|
<meta name="DC.Identifier" content="rbaforzahfprg" />
|
||
|
|
<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>Ensure data integrity with commitment control</title>
|
||
|
|
</head>
|
||
|
|
<body id="rbaforzahfprg"><a name="rbaforzahfprg"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Ensure data integrity with commitment control</h1>
|
||
|
|
<div><p>Commitment control lets you define and process a number of changes
|
||
|
|
to database files in a single unit (transaction). It can ensure that complex
|
||
|
|
application transactions are logically synchronized, even if the job or system
|
||
|
|
ends. Two-phase commitment control ensures that committable resources, such
|
||
|
|
as database files on multiple systems, remain synchronized.</p>
|
||
|
|
<p>You implement commitment control in your database by executing
|
||
|
|
commit and rollback operations. Using SQL, you use the COMMIT and ROLLBACK
|
||
|
|
statements.</p>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<ul class="ullinks">
|
||
|
|
<li class="ulchildlink"><strong><a href="rbafocctrans.htm">Transactions</a></strong><br />
|
||
|
|
A transaction is a group of changes that appear as a single change, such as the transfer of funds from a savings account to a checking account.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rbafoccben.htm">Benefits of using commitment control</a></strong><br />
|
||
|
|
Recovering a complex application requires detailed application knowledge. Programs cannot be restarted. In this case, commitment control helps solve these problems.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rbafoccusg.htm">Usage notes: Commitment control</a></strong><br />
|
||
|
|
The commit and rollback operations are available in several <span class="keyword">iSeries™</span> programming languages, including
|
||
|
|
the RPG/400<sup>®</sup>, COBOL/400<sup>®</sup>,
|
||
|
|
PL/I, SQL, and the i5/OS™ control language (CL). You can open logical files
|
||
|
|
for output under commitment control when underlying physical files are journaled
|
||
|
|
to different journals. Commitment control can also be used in a batch environment.</li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbaforzahfprd.htm" title="The iSeries system uses journaling and commitment control to help you recover data in a database file.">Recover data in a database file</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
||
|
|
<div><a href="../sqlp/rbafydicomm.htm">Commitment control</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relref"><strong>Related reference</strong><br />
|
||
|
|
<div><a href="../db2/rbafzmstc4comit.htm">COMMIT</a></div>
|
||
|
|
<div><a href="../db2/rbafzmstrollbac.htm">ROLLBACK</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|