82 lines
6.0 KiB
HTML
82 lines
6.0 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 with objects" />
|
||
|
|
<meta name="abstract" content="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." />
|
||
|
|
<meta name="description" content="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." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakjconcepts.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakjresourcetypes.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakjlocalremote.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakjintent.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakjprotocol.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakjjrnfiles.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakjsequence.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakjcycle.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakjrecords.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="rzakjresources" />
|
||
|
|
<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 with objects</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzakjresources"><a name="rzakjresources"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">How commitment control works with objects</h1>
|
||
|
|
<div><p>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.</p>
|
||
|
|
<p>The following topics describe these attributes of a committable
|
||
|
|
resource:</p>
|
||
|
|
<ul><li>Resource type</li>
|
||
|
|
<li>Location</li>
|
||
|
|
<li>Commit protocol</li>
|
||
|
|
<li>Access intent</li>
|
||
|
|
</ul>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<ul class="ullinks">
|
||
|
|
<li class="ulchildlink"><strong><a href="rzakjresourcetypes.htm">Types of committable resources</a></strong><br />
|
||
|
|
The table in this topic lists the different types of committable resources.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzakjlocalremote.htm">Local and remote committable resources</a></strong><br />
|
||
|
|
A committable resource can be either a local resource or a remote resource.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzakjintent.htm">Access intent of a committable resource</a></strong><br />
|
||
|
|
The access intent determines how the resources participate together in a transaction.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzakjprotocol.htm">The commit protocol of a committable resource</a></strong><br />
|
||
|
|
<dfn class="term">Commit protocol</dfn> is the capability a resource has to
|
||
|
|
participate in one-phase or two-phase commit processing. Local resources,
|
||
|
|
except API committable resources, are always two-phase resources.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzakjjrnfiles.htm">Journaled files and commitment control</a></strong><br />
|
||
|
|
You must journal (log) a database file (resource type FILE or DDM) before it can be opened for output under commitment control or referenced by an SQL application that uses an isolation level other than No Commit. A file does not need to be journaled in order to open it for input only under commitment control.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzakjsequence.htm">Sequence of journal entries under commitment control</a></strong><br />
|
||
|
|
This table shows the sequence of entries that are typically written while a commitment definition is active. You can use the Journal entry information finder to get more information about the contents of the journal entries.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzakjcycle.htm">Commit cycle identifier</a></strong><br />
|
||
|
|
A <dfn class="term">commit cycle</dfn> is the time from one commitment boundary
|
||
|
|
to the next. The system assigns a <dfn class="term">commit cycle identifier</dfn> to
|
||
|
|
associate all of the journal entries for a particular commit cycle together.
|
||
|
|
Each journal that participates in a transaction has its own commit cycle and
|
||
|
|
its own commit cycle identifier.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzakjrecords.htm">Record locking</a></strong><br />
|
||
|
|
When a job holds a record lock and another job attempts to retrieve that record for update, the requesting job waits and is removed from active processing.</li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<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>
|