67 lines
4.4 KiB
HTML
67 lines
4.4 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="The commit protocol of a committable resource" />
|
||
|
|
<meta name="abstract" content="Commit protocol 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." />
|
||
|
|
<meta name="description" content="Commit protocol 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." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakjresources.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakjiasp.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="rzakjprotocol" />
|
||
|
|
<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>The commit protocol of a committable resource</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzakjprotocol"><a name="rzakjprotocol"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">The commit protocol of a committable resource</h1>
|
||
|
|
<div><p><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.</p>
|
||
|
|
<p>If a committable resource resides on an independent disk pool and the commitment
|
||
|
|
definition resides on a different disk pool, the resource is not considered
|
||
|
|
as a local resource or a two-phase resource.</p>
|
||
|
|
<p>A two-phase resource is also called a <dfn class="term">protected resource</dfn>.
|
||
|
|
Remote resources and API committable resources must be registered
|
||
|
|
as one-phase resources or two-phase resources when they are placed under commitment
|
||
|
|
control. The following table shows what types of committable resources can
|
||
|
|
coexist in a commitment definition with a one-phase resource.</p>
|
||
|
|
|
||
|
|
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" frame="border" border="1" rules="all"><thead align="left"><tr><th valign="top" id="d0e30">Resource type</th>
|
||
|
|
<th valign="top" id="d0e32">Can coexist with</th>
|
||
|
|
</tr>
|
||
|
|
</thead>
|
||
|
|
<tbody><tr><td valign="top" headers="d0e30 ">One-phase API resource</td>
|
||
|
|
<td valign="top" headers="d0e32 ">Other local resources. No remote resources.</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" headers="d0e30 ">One-phase remote resource</td>
|
||
|
|
<td valign="top" headers="d0e32 ">Other one-phase resources at the same location. No local resources.</td>
|
||
|
|
</tr>
|
||
|
|
</tbody>
|
||
|
|
</table>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzakjresources.htm" title="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.">How commitment control works with objects</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
||
|
|
<div><a href="rzakjiasp.htm" title="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.">Commitment control and independent disk pools</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|