76 lines
5.1 KiB
HTML
76 lines
5.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="Commit operation" />
|
|
<meta name="abstract" content="A commit operation makes permanent all changes made under commitment control since the previous commit or rollback operation. The system also releases all locks related to the transaction." />
|
|
<meta name="description" content="A commit operation makes permanent all changes made under commitment control since the previous commit or rollback operation. The system also releases all locks related to the transaction." />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakjrollbacks.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakjcommitdef.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakjsequence.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="rzakjcommitops" />
|
|
<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>Commit operation</title>
|
|
</head>
|
|
<body id="rzakjcommitops"><a name="rzakjcommitops"><!-- --></a>
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|
<h1 class="topictitle1">Commit operation</h1>
|
|
<div><p>A commit operation makes permanent all changes made under commitment
|
|
control since the previous commit or rollback operation. The system also releases
|
|
all locks related to the transaction.</p>
|
|
<p>The system performs the following steps when it receives a request to commit:</p>
|
|
<ul><li>The system saves the commit identification, if one is provided, for use
|
|
at recovery time.</li>
|
|
<li>The system writes records to the file before performing the commit operation
|
|
if both of the following are true: <ul><li>Records were added to a local or remote database file under commitment
|
|
control.</li>
|
|
<li>SEQONLY(*YES) was specified when the file was opened so that blocked I/O
|
|
feedback is used by the system and a partial block of records exists.</li>
|
|
</ul>
|
|
<p>Otherwise, the I/O feedback area and I/O buffers are not changed.</p>
|
|
</li>
|
|
<li>The system makes a call to the commit and rollback exit program for each
|
|
API commitment resource that is present in the commitment definition. If a
|
|
location has more than one exit program registered, the system calls exit
|
|
programs for that location in the order that they were registered.</li>
|
|
<li>If any record changes were made to resources assigned to
|
|
a journal, the system writes a C CM journal entry to every local journal associated
|
|
with the commitment definition. Sequence of journal entries under commitment
|
|
control shows the entries that are typically written while a commitment definition
|
|
is active.</li>
|
|
<li>The system makes permanent object-level changes that are pending.</li>
|
|
<li>The system unlocks record and object locks that were acquired and kept
|
|
for commitment control purposes. Those resources are made available to other
|
|
users.</li>
|
|
<li>The system changes information in the commitment definition to show that
|
|
the current transaction has been ended.</li>
|
|
</ul>
|
|
<p>The system must perform all of the previous steps correctly for the commit
|
|
operation to be successful.</p>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzakjrollbacks.htm" title="Commit and rollback operations affect changes that are made under commitment control.">How commit and rollback operations work</a></div>
|
|
</div>
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
|
<div><a href="rzakjcommitdef.htm" title="You create a commitment definition when you use the Start Commitment Control (STRCMTCTL) command to start commitment control on your system. Also, DB2 Universal Database (UDB) for iSeries automatically creates a commitment definition when the isolation level is other than No Commit.">Commitment definition</a></div>
|
|
<div><a href="rzakjsequence.htm" title="This table shows the sequence of entries that are typically written while a commitment definition is active. You can use the Journal entry information finder to get more information about the contents of the journal entries.">Sequence of journal entries under commitment control</a></div>
|
|
</div>
|
|
</div>
|
|
</body>
|
|
</html> |