86 lines
5.2 KiB
HTML
86 lines
5.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="How commitment control works" />
|
|
<meta name="abstract" content="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." />
|
|
<meta name="description" content="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." />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakjconcepts.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="rzakjhowworks" />
|
|
<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>How commitment control works</title>
|
|
</head>
|
|
<body id="rzakjhowworks"><a name="rzakjhowworks"><!-- --></a>
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|
<h1 class="topictitle1">How commitment control works</h1>
|
|
<div><p>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.</p>
|
|
<p>Commitment control ensures that either the entire group of individual changes
|
|
occur on all systems that participate or that none of the changes occur. For
|
|
example, when you transfer funds from a savings to a checking account, more
|
|
than one change occurs as a group. To you, this transfer seems like a single
|
|
change. However, more than one change occurs to the database because both
|
|
savings and checking accounts are updated. To keep both accounts accurate,
|
|
either all the changes or none of the changes must occur to the checking and
|
|
savings account.</p>
|
|
<p>Commitment control allows you to:</p>
|
|
<ul><li>Ensure that all changes within a transaction are completed for all resources
|
|
that are affected.</li>
|
|
<li>Ensure that all changes within a transaction are removed if processing
|
|
is interrupted.</li>
|
|
<li>Remove changes that are made during a transaction when the application
|
|
determines that a transaction is in error.</li>
|
|
</ul>
|
|
<p>You can also design an application so that commitment control can restart
|
|
the application if a job, an activation group within a job, or the system
|
|
ends abnormally. With commitment control, you can have assurance that when
|
|
the application starts again, no partial updates are in the database due to
|
|
incomplete transactions from a prior failure.</p>
|
|
<div class="section"><h4 class="sectiontitle">Transaction</h4><p>A transaction is a group of individual
|
|
changes to objects on the system that appears as a single atomic change to
|
|
the user.</p>
|
|
<div class="note"><span class="notetitle">Note:</span> iSeries™ navigator uses the term<em> transaction</em>,
|
|
whereas the character-based interface uses the term<em> Logical Unit of Work
|
|
(LUW)</em>. The two terms are interchangeable. This topic, unless specifically
|
|
referring to the character-based interface, uses the term transaction.</div>
|
|
<p>A transaction can be any of the following situations:</p>
|
|
<ul><li>Inquiries in which no database file changes occur.</li>
|
|
<li>Simple transactions that change one database file.</li>
|
|
<li>Complex transactions that changes one or more database files.</li>
|
|
<li>Complex transactions that change one or more database files, but these
|
|
changes represent only a part of a logical group of transactions.</li>
|
|
<li>Simple or complex transactions that involve database files at more than
|
|
one location. The database files can be: <ul><li>On a single remote system.</li>
|
|
<li>On the local system and one or more remote systems.</li>
|
|
<li>Assigned to more than one journal on the local system. Each journal can
|
|
be thought of as a <dfn class="term">local location</dfn>.</li>
|
|
</ul>
|
|
</li>
|
|
<li>Simple or complex transactions on the local system that involve objects
|
|
other than database files.</li>
|
|
</ul>
|
|
</div>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzakjconcepts.htm" title="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.">Commitment control concepts</a></div>
|
|
</div>
|
|
</div>
|
|
</body>
|
|
</html> |