64 lines
4.3 KiB
HTML
64 lines
4.3 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="Journals" />
|
||
|
|
<meta name="abstract" content="When a change is made to a file and you are using journals, the system records the change in a journal receiver and writes the receiver to auxiliary storage before it is recorded in the file. Therefore, the journal receiver always has the latest database information." />
|
||
|
|
<meta name="description" content="When a change is made to a file and you are using journals, the system records the change in a journal receiver and writes the receiver to auxiliary storage before it is recorded in the file. Therefore, the journal receiver always has the latest database information." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbaforzahfpre.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../rzaki/rzakikickoff.htm" />
|
||
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 1998, 2006" />
|
||
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 1998, 2006" />
|
||
|
|
<meta name="DC.Format" content="XHTML" />
|
||
|
|
<meta name="DC.Identifier" content="rbaforzahfprf" />
|
||
|
|
<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>Journals</title>
|
||
|
|
</head>
|
||
|
|
<body id="rbaforzahfprf"><a name="rbaforzahfprf"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Journals</h1>
|
||
|
|
<div><p>When a change is made to a file and you are using journals, the
|
||
|
|
system records the change in a journal receiver and writes the receiver to
|
||
|
|
auxiliary storage before it is recorded in the file. Therefore, the journal
|
||
|
|
receiver always has the latest database information.</p>
|
||
|
|
<p>Journal entries record activity for a specific record or for the file as
|
||
|
|
a whole. Each entry includes bytes of control information that identify the
|
||
|
|
source of the activity (such as user, job, program, time, and date). For changes
|
||
|
|
that affect a single record, record images are included after the control
|
||
|
|
information. The record image before the change can also be included. You
|
||
|
|
can control whether to create a journal both before and after record images
|
||
|
|
or just after record images by specifying the IMAGES parameter on the Start
|
||
|
|
Journal Physical File (STRJRNPF) command.</p>
|
||
|
|
<p>All journaled database files are automatically synchronized with the journal
|
||
|
|
when the system is started (IPL time). If the system session ends
|
||
|
|
abnormally, some database changes might be in the journal, but some of these
|
||
|
|
changes might not be reflected in the database files. If that is the case,
|
||
|
|
the system automatically updates the database files from the journal.</p>
|
||
|
|
<p>Journals make saving database files an easier and faster task. For example,
|
||
|
|
instead of saving an entire file every day, save the journal receiver that
|
||
|
|
contains the changes to that file. You can still save the entire file on a
|
||
|
|
weekly basis. This method can reduce the amount of time it takes to perform
|
||
|
|
your daily save operations.</p>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbaforzahfpre.htm" title="Journal management allows you to record all the data changes that occur to one or more database files. You can then use the journal for recovery.">Manage journals</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>
|