105 lines
6.4 KiB
HTML
105 lines
6.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="Error conditions" />
|
||
|
|
<meta name="abstract" content="If an error occurs, an escape message that you can monitor for in a program is sent." />
|
||
|
|
<meta name="description" content="If an error occurs, an escape message that you can monitor for in a program is sent." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakjcommiterror.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="rzakjerrorcondition" />
|
||
|
|
<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>Error conditions</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzakjerrorcondition"><a name="rzakjerrorcondition"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Error conditions</h1>
|
||
|
|
<div><p>If an error occurs, an escape message that you can monitor for
|
||
|
|
in a program is sent.</p>
|
||
|
|
<p>Here are some typical errors related to commitment control:</p>
|
||
|
|
<ul><li>Consecutive STRCMTCTL commands are run without an intervening ENDCMTCTL
|
||
|
|
command.</li>
|
||
|
|
<li>Files are opened under commitment control, but no STRCMTCTL command was
|
||
|
|
run. <p>This is not an error condition for programs that run within an activation
|
||
|
|
group that are to use the job-level commitment definition. The job-level commitment
|
||
|
|
definition can be started only by a single program, but when started by a
|
||
|
|
program, the job-level commitment definition is used by any program running
|
||
|
|
in any activation group that is not using an activation-group-level commitment
|
||
|
|
definition. Programs that run within an activation group that are to use the
|
||
|
|
activation-group-level commitment definition must first start the activation-group-level
|
||
|
|
commitment definition with the STRCMTCTL command.</p>
|
||
|
|
</li>
|
||
|
|
<li>Files that are opened for output under commitment control are not journaled.</li>
|
||
|
|
<li>The first open operation of a shared file places the file under commitment
|
||
|
|
control, but subsequent open operations of the same shared file do not.</li>
|
||
|
|
<li>The first open operation of a shared file does not place the file under
|
||
|
|
commitment control, but subsequent open operations of the same shared file
|
||
|
|
do.</li>
|
||
|
|
<li>The record lock limit for the job is reached in a single transaction.</li>
|
||
|
|
<li>The program issues a read operation, a commit operation, and a change
|
||
|
|
to the same record. The read operation must be issued again after the commit
|
||
|
|
operation because the commit operation has freed the lock on the record.</li>
|
||
|
|
<li>For a one-phase location, resources placed under commitment control do
|
||
|
|
not reside at the same location as resources already under commitment control
|
||
|
|
for the commitment definition.</li>
|
||
|
|
<li>Uncommitted changes exist when an ENDCMTCTL command is issued. <p>This
|
||
|
|
is not an error condition for the ENDCMTCTL command if all files are closed,
|
||
|
|
any remote database is disconnected, and no API commitment resource is still
|
||
|
|
associated with the commitment definition to be ended.</p>
|
||
|
|
</li>
|
||
|
|
<li>A commit, rollback, or ENDCMTCTL command is run, and a STRCMTCTL command
|
||
|
|
was not run. <p>This is not an error condition for programs that run within
|
||
|
|
an activation group and the job-level commitment definition is active. The
|
||
|
|
job-level commitment definition can be started only by a single program, but
|
||
|
|
when started by a program, the job-level commitment definition is used by
|
||
|
|
any program running in any activation group that is not using an activation-group-level
|
||
|
|
commitment definition. Programs that run within an activation group and are
|
||
|
|
to use the activation-group-level commitment definition must first start the
|
||
|
|
activation-group-level commitment definition with the STRCMTCTL command.</p>
|
||
|
|
</li>
|
||
|
|
<li>An ENDCMTCTL command is run with files still open under commitment control
|
||
|
|
for the commitment definition.</li>
|
||
|
|
<li>A job performing a save operation has one or more commitment definitions
|
||
|
|
that are not at a commitment boundary.</li>
|
||
|
|
<li>A save-while-active operation ended because other jobs with committable
|
||
|
|
resources did not reach a commitment boundary in the time specified for the
|
||
|
|
SAVACTWAIT parameter.</li>
|
||
|
|
<li>A save-while-active process was not able to continue because of API committable
|
||
|
|
resources being added to more than one commitment definition for a single
|
||
|
|
job.</li>
|
||
|
|
<li>More than 1023 commitment definitions exist for a single job.</li>
|
||
|
|
<li>The conversation to a remote location is lost due to a resource failure.
|
||
|
|
This might cause the transaction to be rolled back.</li>
|
||
|
|
<li>A one-phase resource that is opened for update is present at a node that
|
||
|
|
did not initiate the commit operation. You must remove either the resource
|
||
|
|
or the node that initiated the commit request.</li>
|
||
|
|
<li>A commit operation is requested while the transaction is in rollback required
|
||
|
|
(RBR) state. A rollback operation must be done.</li>
|
||
|
|
<li>An API exit program issues a commit request or a rollback request.</li>
|
||
|
|
<li>A trigger program issues a commit request or a rollback request for the
|
||
|
|
commitment definition under which the trigger program was called.</li>
|
||
|
|
</ul>
|
||
|
|
<p>The trigger program can start a separate commitment definition and issue
|
||
|
|
a commit or rollback request for that definition.</p>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzakjcommiterror.htm" title="When you use commitment control, it is important to understand which conditions cause errors and which do not.">Commitment control errors</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|