84 lines
6.1 KiB
HTML
84 lines
6.1 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 control errors" />
|
|
<meta name="abstract" content="When you use commitment control, it is important to understand which conditions cause errors and which do not." />
|
|
<meta name="description" content="When you use commitment control, it is important to understand which conditions cause errors and which do not." />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakjtrouble.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakjerrorcondition.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakjnonerror.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakjerrormessage.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakjerrorcall.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakjnormcommit.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakjnowaitoutcome.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakjstates.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="rzakjcommiterror" />
|
|
<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 control errors</title>
|
|
</head>
|
|
<body id="rzakjcommiterror"><a name="rzakjcommiterror"><!-- --></a>
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|
<h1 class="topictitle1">Commitment control errors</h1>
|
|
<div><p>When you use commitment control, it is important to understand
|
|
which conditions cause errors and which do not.</p>
|
|
<p>In general, errors occur when commitment control functions are used inconsistently,
|
|
such as running an End Commitment Control (ENDCMTCTL) command when files that
|
|
use the commitment definition are still open.</p>
|
|
<div class="section"><h4 class="sectiontitle">Errors during commit processing</h4><p>If a communications
|
|
or system failure occurs during a commit operation, resynchronization might
|
|
need to be performed to ensure that the transaction managers keep the data
|
|
consistent on all the systems involved in the transaction. The behavior of
|
|
the resynchronization and how it affects the commit operation depends on these
|
|
factors :</p>
|
|
<ul><li>The <samp class="codeph">Wait for outcome</samp> commitment option.</li>
|
|
<li>The state of the transaction.</li>
|
|
</ul>
|
|
<p>If the failure is catastrophic such that it can never be repaired,
|
|
or it cannot be repaired in a timely manner, the system operators for other
|
|
systems involved in the transaction must make a heuristic decision. The heuristic
|
|
decision commits or rolls back the changes made on that system during the
|
|
transaction. If the failure is repaired after such a decision, and the resynchronization
|
|
detects that the decision caused data integrity problems, message CPD83D9
|
|
or CPD83E9 is sent to the QSYSOPR message queue.</p>
|
|
</div>
|
|
</div>
|
|
<div>
|
|
<ul class="ullinks">
|
|
<li class="ulchildlink"><strong><a href="rzakjerrorcondition.htm">Error conditions</a></strong><br />
|
|
If an error occurs, an escape message that you can monitor for in a program is sent.</li>
|
|
<li class="ulchildlink"><strong><a href="rzakjnonerror.htm">Non-error conditions</a></strong><br />
|
|
This topic lists situations that appear to have the potential to cause an error message. However, commitment control allows these situations in which no error occurs.</li>
|
|
<li class="ulchildlink"><strong><a href="rzakjerrormessage.htm">Error messages to monitor for during commitment control</a></strong><br />
|
|
Several different error messages can be returned by the commit or rollback operations or sent to the job log, depending on the type of message and when the error occurred.</li>
|
|
<li class="ulchildlink"><strong><a href="rzakjerrorcall.htm">Monitor for errors after a CALL command</a></strong><br />
|
|
When a program that uses commitment control is called, monitor for unexpected errors and perform a rollback operation if an error occurs.</li>
|
|
<li class="ulchildlink"><strong><a href="rzakjnormcommit.htm">Failure of normal commit or rollback processing</a></strong><br />
|
|
Errors might occur at any time during commit or rollback processing.</li>
|
|
</ul>
|
|
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzakjtrouble.htm" title="You can read this information when you need to troubleshoot commitment control.">Troubleshoot transactions and commitment control</a></div>
|
|
</div>
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
|
<div><a href="rzakjnowaitoutcome.htm" title="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.">Commitment definition for two-phase commit: Not wait for outcome</a></div>
|
|
<div><a href="rzakjstates.htm" title="A commitment definition is established at each location that is part of the transaction program network. For each commitment definition, the system keeps track of the state of its current transaction and previous transaction.">States of the transaction for two-phase commitment control</a></div>
|
|
</div>
|
|
</div>
|
|
</body>
|
|
</html> |