80 lines
5.0 KiB
HTML
80 lines
5.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="Non-error conditions" />
|
||
|
|
<meta name="abstract" content="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." />
|
||
|
|
<meta name="description" content="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." />
|
||
|
|
<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="rzakjnonerror" />
|
||
|
|
<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>Non-error conditions</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzakjnonerror"><a name="rzakjnonerror"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Non-error conditions</h1>
|
||
|
|
<div><p>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.</p>
|
||
|
|
<p>Here are some situations for commitment control in which
|
||
|
|
no errors occur:</p>
|
||
|
|
<ul><li>A commit or rollback operation is run and no resources are under commitment
|
||
|
|
control. This allows you to include commit or rollback operations in your
|
||
|
|
program without considering whether there are resources under commitment control.
|
||
|
|
It also allows you to specify a commit identification before making any committable
|
||
|
|
changes.</li>
|
||
|
|
<li>A commit or rollback operation is run and there are no uncommitted resource
|
||
|
|
changes. This allows you to include commit and rollback operations within
|
||
|
|
your program without considering whether there are uncommitted resource changes.</li>
|
||
|
|
<li>A file under commitment control is closed and uncommitted records exist.
|
||
|
|
This situation allows another program to be called to perform the commit or
|
||
|
|
rollback operation. This occurs regardless of whether the file is shared.
|
||
|
|
This function allows a subprogram to make database changes that are part of
|
||
|
|
a transaction involving multiple programs.</li>
|
||
|
|
<li>A job ends, either normally or abnormally, with uncommitted changes for
|
||
|
|
one or more commitment definitions. The changes for all commitment definitions
|
||
|
|
are rolled back.</li>
|
||
|
|
<li>An activation group ends with pending changes for the activation-group-level
|
||
|
|
commitment definition. If the activation group is ending normally and there
|
||
|
|
are no errors encountered when closing any files opened under commitment control
|
||
|
|
scoped to the same activation group that is ending, an implicit
|
||
|
|
commit is performed by the system. Otherwise, an implicit rollback is performed.</li>
|
||
|
|
<li>A program accesses a changed record again that has not been committed.
|
||
|
|
This allows a program to: <ul><li>Add a record and update it before specifying the commit operation.</li>
|
||
|
|
<li>Update the same record twice before specifying the commit operation.</li>
|
||
|
|
<li>Add a record and delete it before specifying the commit operation.</li>
|
||
|
|
<li>Access an uncommitted record again by a different logical file (under
|
||
|
|
commitment control).</li>
|
||
|
|
</ul>
|
||
|
|
</li>
|
||
|
|
<li>You specify LCKLVL(*CHG or *CS) on the STRCMTCTL command and open a file
|
||
|
|
with a commit operation for read-only. In this case, no locks occur on the
|
||
|
|
request. It is treated as if commitment control is not in effect, but the
|
||
|
|
file does appear on the WRKJOB menu option of files under commitment control.</li>
|
||
|
|
<li>You issue the STRCMTCTL command and do not open any files under commitment
|
||
|
|
control. In this situation, any record-level changes made to the files are
|
||
|
|
not made under commitment control.</li>
|
||
|
|
</ul>
|
||
|
|
</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>
|