73 lines
5.1 KiB
HTML
73 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="Journaled files and commitment control" />
|
||
|
|
<meta name="abstract" content="You must journal (log) a database file (resource type FILE or DDM) before it can be opened for output under commitment control or referenced by an SQL application that uses an isolation level other than No Commit. A file does not need to be journaled in order to open it for input only under commitment control." />
|
||
|
|
<meta name="description" content="You must journal (log) a database file (resource type FILE or DDM) before it can be opened for output under commitment control or referenced by an SQL application that uses an isolation level other than No Commit. A file does not need to be journaled in order to open it for input only under commitment control." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakjresources.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../rzaki/rzakikickoff.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="rzakjjrnfiles" />
|
||
|
|
<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>Journaled files and commitment control</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzakjjrnfiles"><a name="rzakjjrnfiles"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Journaled files and commitment control</h1>
|
||
|
|
<div><p>You must journal (log) a database file (resource type FILE or DDM)
|
||
|
|
before it can be opened for output under commitment control or referenced
|
||
|
|
by an SQL application that uses an isolation level other than No Commit. A
|
||
|
|
file does not need to be journaled in order to open it for input only under
|
||
|
|
commitment control.</p>
|
||
|
|
<p>An error occurs if:</p>
|
||
|
|
<ul><li>An attempt is made to open a database file for output under commitment
|
||
|
|
control, but the file is not currently journaled.</li>
|
||
|
|
<li>No commitment definition is started that can be used by the file being
|
||
|
|
opened under commitment control.</li>
|
||
|
|
</ul>
|
||
|
|
<p>If only the after images are being journaled for a database file when that
|
||
|
|
file is opened under commitment control, the system automatically starts journaling
|
||
|
|
both the before and after images. The before images are written only for changes
|
||
|
|
to the file that occur under commitment control. If other changes that are
|
||
|
|
not under commitment control occur to the file at the same time, only after-images
|
||
|
|
are written for those changes.</p>
|
||
|
|
<p>The system automatically writes record-level committable changes and object-level
|
||
|
|
committable changes to a journal. For record-level changes, the system then
|
||
|
|
uses the journal entries, if necessary, for recovery purposes; the system
|
||
|
|
does not use entries from object-level committable changes for recovery purposes.
|
||
|
|
Furthermore, the system does not automatically write journal entries for API
|
||
|
|
commitment resources. However, the exit program for the API resource can use
|
||
|
|
the Send Journal Entry (QJOSJRNE) API to write journal entries to provide
|
||
|
|
an audit trail or to assist with recovery. The content of these entries is
|
||
|
|
controlled by the user exit program.</p>
|
||
|
|
<p>The system uses a technique other than a journal to perform recovery for
|
||
|
|
object-level commitment resources. Recovery for API commitment resources is
|
||
|
|
accomplished by calling the commit and rollback exit program associated with
|
||
|
|
each particular API commitment resource. The exit program has the responsibility
|
||
|
|
for performing the actual recovery that is necessary for the situation.</p>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzakjresources.htm" title="When you place an object under commitment control, it becomes a committable resource. It is registered with the commitment definition. It participates in each commit operation and rollback operation that occurs for that commitment definition.">How commitment control works with objects</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
||
|
|
<div><a href="../rzaki/rzakikickoff.htm">Journal management</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|