66 lines
5.3 KiB
HTML
66 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="Commitment definitions for two-phase commitment control" />
|
||
|
|
<meta name="abstract" content="After you start commitment control, you can use the Change Commitment Options (QTNCHGCO) API to change the commitment options for your transaction." />
|
||
|
|
<meta name="description" content="After you start commitment control, you can use the Change Commitment Options (QTNCHGCO) API to change the commitment options for your transaction." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakjtwophase.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakjallowrdonly.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakjnowaitoutcome.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakjokleaveout.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakjnolastagent.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakjvotereliable.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../apis/QTNCHGCO.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="rzakjcommitdefs_tp" />
|
||
|
|
<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>Commitment definitions for two-phase commitment control</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzakjcommitdefs_tp"><a name="rzakjcommitdefs_tp"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Commitment definitions for two-phase commitment control</h1>
|
||
|
|
<div><p>After you start commitment control, you can use the Change Commitment
|
||
|
|
Options (QTNCHGCO) API to change the commitment options for your transaction.</p>
|
||
|
|
<p>Depending on your environment and your applications, changing the commitment
|
||
|
|
options can improve your system's performance.</p>
|
||
|
|
<div class="note"><span class="notetitle">Note:</span> If you are using a DRDA<sup>®</sup> distributed unit of work over TCP/IP connection,
|
||
|
|
the only option that applies is Allow vote read-only.</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<ul class="ullinks">
|
||
|
|
<li class="ulchildlink"><strong><a href="rzakjallowrdonly.htm">Commitment definition for two-phase commit: Allow vote read-only</a></strong><br />
|
||
|
|
Normally, a transaction manager participates in both phases of commit processing. To improve the performance of commit processing, you can set up some or all locations in a transaction to allow the transaction manager to vote read-only.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzakjnowaitoutcome.htm">Commitment definition for two-phase commit: Not wait for outcome</a></strong><br />
|
||
|
|
When a communication or system failure occurs during a commit operation so that resynchronization is required, the default is to wait until the resynchronization is finished before the commit operation completes.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzakjokleaveout.htm">Commitment definition for two-phase commit: Indicate OK to leave out</a></strong><br />
|
||
|
|
Normally, the transaction manager at every location in the transaction program network participates in every commit or rollback operation. To improve performance, you can set up some or all locations in a transaction to allow the transaction manager to indicate OK to leave out.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzakjnolastagent.htm">Commitment definition for two-phase commit: Not select a last agent</a></strong><br />
|
||
|
|
By default, the transaction manager for the initiator is free to select any agent as a last agent during a commit operation.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzakjvotereliable.htm">Vote reliable effect on flow of commit processing</a></strong><br />
|
||
|
|
Vote reliable is an optimization that improves performance by returning earlier to the initiator application after a commit operation and eliminating one message during a commit operation.</li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzakjtwophase.htm" title="Two-phase commitment control ensures that committable resources on multiple systems remain synchronized.">Two-phase commitment control</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relref"><strong>Related reference</strong><br />
|
||
|
|
<div><a href="../apis/QTNCHGCO.htm">Change Commitment Options (QTNCHGCO) API</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|