62 lines
4.8 KiB
HTML
62 lines
4.8 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="Usage notes: Commitment control" />
|
||
|
|
<meta name="abstract" content="The commit and rollback operations are available in several iSeries programming languages, including the RPG/400, COBOL/400, 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." />
|
||
|
|
<meta name="description" content="The commit and rollback operations are available in several iSeries programming languages, including the RPG/400, COBOL/400, 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." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbaforzahfprg.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../sqlp/rbafydicomm.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="rbafoccusg" />
|
||
|
|
<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>Usage notes: Commitment control</title>
|
||
|
|
</head>
|
||
|
|
<body id="rbafoccusg"><a name="rbafoccusg"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Usage notes: Commitment control</h1>
|
||
|
|
<div><p>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.</p>
|
||
|
|
<p>However, the checks for violations are deferred if a record change affects
|
||
|
|
underlying physical files that are journaled to the same journal.
|
||
|
|
If the record change affects underlying physical files that are not journaled
|
||
|
|
to the same journal, and it causes a duplicate key or referential constraint
|
||
|
|
violation, an error will occur during the input/output operation. For example,
|
||
|
|
assume physical file A with a unique key is journaled to journal X, while
|
||
|
|
physical file B with a unique key is journaled to journal Y. Logical file
|
||
|
|
C is created over physical files A and B and opened under commitment control.
|
||
|
|
A delete operation performed using logical file C removes a record from physical
|
||
|
|
file A with key K. It is possible to add a record back to physical file A
|
||
|
|
with key K before the transaction is committed. However, an attempt to add
|
||
|
|
a record to physical file B with key K, before the transaction is committed,
|
||
|
|
will fail since physical files A and B are journaled to different journals.</p>
|
||
|
|
<p>Just as it provides assistance in interactive transaction recovery, commitment
|
||
|
|
control can also help in batch job recovery. </p>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbaforzahfprg.htm" title="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.">Ensure data integrity with commitment control</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
||
|
|
<div><a href="../sqlp/rbafydicomm.htm">Commitment control</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|