73 lines
7.0 KiB
HTML
73 lines
7.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="Reasons to journal before-images" />
|
||
|
|
<meta name="abstract" content="When you journal an object, the system always writes an after-image for every change that is made. You can request that the system write before-image journal entries for database files and data areas. All other object types only journal after-images. This significantly increases the auxiliary storage requirements for journaling." />
|
||
|
|
<meta name="description" content="When you journal an object, the system always writes an after-image for every change that is made. You can request that the system write before-image journal entries for database files and data areas. All other object types only journal after-images. This significantly increases the auxiliary storage requirements for journaling." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakiplnobjrn.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../cl/rmvjrnchg.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../cl/cmpjrnimg.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakismappintro.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakistrjrnpf.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakistrjrndta.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../cl/chgjrnobj.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakistrjrnpf.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="rzakijrnbi" />
|
||
|
|
<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>Reasons to journal before-images</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzakijrnbi"><a name="rzakijrnbi"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Reasons to journal before-images</h1>
|
||
|
|
<div><p>When you journal an object, the system always writes an after-image for every change that is made. You can request that the system write before-image journal entries for database files and data
|
||
|
|
areas. All other object types only journal after-images. This significantly increases the auxiliary storage requirements for journaling.</p>
|
||
|
|
<p>However, you can choose to journal before-images for these reasons:</p>
|
||
|
|
<ul><li>Before-images are required for a backout recovery, where you remove journal changes with the Remove Journaled Changes (RMVJRNCHG) command rather than applying journal changes to a restored copy of
|
||
|
|
an object. Backout recovery is often complex, particularly if multiple users and programs are accessing the same object. It is most commonly used when new applications or programs are being tested.</li>
|
||
|
|
<li>For database physical files, before-images are required to use the Compare Journal Images (CMPJRNIMG) command. This command highlights the differences between the before-images and after-images. It
|
||
|
|
is sometimes used to audit changes to a database file.</li>
|
||
|
|
<li>For database physical files, if you want a copy of the record that is deleted to be part of the deleted record journal entry information, you must specify before-images.</li>
|
||
|
|
<li>Commitment control requires before-images for the system to roll back uncommitted changes. When you open a database file under commitment control, the system automatically journals both before-images
|
||
|
|
and after-images while the commitment definition is active. If you normally journal only after-images, the system writes before-images only for the changes made under commitment control. If the system initiates
|
||
|
|
the journaling of before-images, you cannot use them to remove journaled changes. Commitment control does not support integrated file system objects, data areas, or data queues. </li>
|
||
|
|
<li>Access path journaling also requires before-images for the system to use for IPL recovery. When you journal access paths, or the system journals an access path to provide system-managed access-path
|
||
|
|
protection, the system will automatically journal both before and after-images. If you normally journal only after-images, the system also writes before-images if you are journaling the access path. </li>
|
||
|
|
</ul>
|
||
|
|
<p>You can select before-images on an object-by-object basis. You specify whether you want after-images or both when you start journaling for a database file or a data area. After you start journaling a
|
||
|
|
database file or a data area, you can use the Change Journal Object (CHGJRNOBJ) command to change whether you are journaling before-images. </p>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <img src="./delta.gif" alt="Start of change" /><a href="rzakiplnobjrn.htm" title="When you plan which objects to journal, consider the following:">Plan which objects to journal</a><img src="./deltaend.gif" alt="End of change" /></div>
|
||
|
|
</div>
|
||
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
||
|
|
<div><a href="rzakismappintro.htm" title="System-managed access-path protection (SMAPP) allows you to use some of the advantages of journaling without explicitly setting up journaling. Use SMAPP to decrease the time it takes to restart your system after an abnormal end.">System-managed access-path protection</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="reltasks"><strong>Related tasks</strong><br />
|
||
|
|
<div><a href="rzakistrjrnpf.htm" title="When you start journaling a physical file (table), you specify whether you want after-images saved, or both before-images and after-images.">Journal database physical files (tables)</a></div>
|
||
|
|
<div><a href="rzakistrjrndta.htm" title="When you start journaling for a data area or a data queue, the system writes journal entries for all changes to the data area or data queue.">Journal data areas and data queues</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relref"><strong>Related reference</strong><br />
|
||
|
|
<div><a href="../cl/rmvjrnchg.htm">Remove Journaled Changes (RMVJRNCHG) command</a></div>
|
||
|
|
<div><a href="../cl/cmpjrnimg.htm">Compare Journal Images (CMPJRNIMG) command</a></div>
|
||
|
|
<div><a href="../cl/chgjrnobj.htm">Change Journaled Object (CHGJRNOBJ) command</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|