124 lines
8.7 KiB
HTML
124 lines
8.7 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="Journal entries" />
|
||
|
|
<meta name="abstract" content="When you use journal management, the system keeps a record of changes that you make to objects that are journaled and of other events that occur on the system. These records are called journal entries. You can use journal entries to help recover objects or analyze changes that were made to the objects." />
|
||
|
|
<meta name="description" content="When you use journal management, the system keeps a record of changes that you make to objects that are journaled and of other events that occur on the system. These records are called journal entries. You can use journal entries to help recover objects or analyze changes that were made to the objects." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakiconcepts.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakiwhysavjrn.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../cl/apyjrnchg.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../cl/apyjrnchgx.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../cl/cmpjrnimg.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../apis/QJODLTPH.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../cl/dspjrn.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../apis/getpthff.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../cl/rcvjrne.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../cl/rtvjrne.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../apis/QJORJRNE.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../cl/rmvjrnchg.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../apis/qdbrplay.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../cl/sndjrne.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../apis/QJOSJRNE.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakijrnentry.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="rzakijrnentryconcepts" />
|
||
|
|
<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>Journal entries</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzakijrnentryconcepts"><a name="rzakijrnentryconcepts"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Journal entries</h1>
|
||
|
|
<div><p>When you use journal management, the system keeps a record of changes
|
||
|
|
that you make to objects that are journaled and of other events that occur
|
||
|
|
on the system. These records are called journal entries. You can use journal
|
||
|
|
entries to help recover objects or analyze changes that were made to the objects.</p>
|
||
|
|
<p>Every journal entry is stored internally in a compressed format. The operating
|
||
|
|
system must convert journal entries to an external form before you can see
|
||
|
|
them. You cannot change or access the journal entries directly. Not even the
|
||
|
|
security officer can remove or change journal entries in a journal receiver.
|
||
|
|
You can use these journal entries to help you recover your objects or analyze
|
||
|
|
changes that were made to the objects.</p>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Contents of a journal entry</h4><p>Journal entries contain
|
||
|
|
the following information:</p>
|
||
|
|
<ul><li>Information that identifies the type of change.</li>
|
||
|
|
<li>Information that identifies the data that was changed.</li>
|
||
|
|
<li>The after-image of the data.</li>
|
||
|
|
<li>Optionally, the before-image of the data (this is a separate entry in
|
||
|
|
the journal).</li>
|
||
|
|
<li>Information that identifies the job, the user, and the time of change.</li>
|
||
|
|
<li>The journal identifier of the object.</li>
|
||
|
|
<li>Information that indicates if the entry-specific data is minimized.</li>
|
||
|
|
</ul>
|
||
|
|
<p>The system also places entries in the journal that are not for a particular
|
||
|
|
journaled object. These entries contain information about the operation of
|
||
|
|
the system and the control of the journal receivers.</p>
|
||
|
|
</div>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Journal identifier</h4><p>When you start journaling an
|
||
|
|
object, the system assigns a unique <span class="uicontrol">journal identifier</span> (JID)
|
||
|
|
to that object. The system uses the JID to associate the journal entry with
|
||
|
|
the corresponding journaled object.</p>
|
||
|
|
</div>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Journal entry numbering</h4><p>Each journal entry is sequentially
|
||
|
|
numbered without any missing numbers until you reset the sequence number with
|
||
|
|
the <span class="cmdname">Change Journal (CHGJRN)</span> command or iSeries™ Navigator.
|
||
|
|
However, when you display journal entries, sequence numbers can be missing
|
||
|
|
because the system uses some entries only internally. For audit purposes,
|
||
|
|
you can display these internal entries with the INCHIDENT option on the <span class="cmdname">Display
|
||
|
|
Journal (DSPJRN)</span> command. </p>
|
||
|
|
<p>When the system exceeds the largest
|
||
|
|
sequence number, a message is sent to the system operator identifying the
|
||
|
|
condition and requesting action. No other journal entries can be added to
|
||
|
|
the journal until the journal receivers are changed and the sequence number
|
||
|
|
is reset.</p>
|
||
|
|
</div>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Fixed-length and variable-length portions</h4><p>A journal
|
||
|
|
entry that is converted for displaying or processing contains a fixed-length
|
||
|
|
prefix portion that is followed by a variable-length portion. The variable-length
|
||
|
|
portion contains entry-specific data and, in some cases, null-values indicator
|
||
|
|
data. The format of the converted entry depends on the command that you use
|
||
|
|
and the format that you specify. The entry-specific data varies by entry type.
|
||
|
|
The <span class="cmdname">Send Journal Entry (SNDJRNE)</span> command or the <span class="apiname">QJOSJRNE</span> API
|
||
|
|
specifies the entry-specific data for user-created journal entries.</p>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzakiconcepts.htm" title="This topic explains how journal management works, why to use it, and how it affects your system.">Journal management concepts</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
||
|
|
<div><a href="rzakiwhysavjrn.htm" title="After you start journaling, it is essential that you save objects that you are journaling.">Why you must save objects after you start journaling</a></div>
|
||
|
|
<div><a href="rzakijrnentry.htm" title="This topic provides information and tasks for working with journal entries.">Journal entry information</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relref"><strong>Related reference</strong><br />
|
||
|
|
<div><a href="../cl/apyjrnchg.htm">Apply Journaled Changes (APYJRNCHG) command</a></div>
|
||
|
|
<div><a href="../cl/apyjrnchgx.htm">Apply Journaled Changes Extend (APYJRNCHGX) command</a></div>
|
||
|
|
<div><a href="../cl/cmpjrnimg.htm">Compare Journal Images (CMPJRNIMG) command</a></div>
|
||
|
|
<div><a href="../apis/QJODLTPH.htm">Delete Pointer Handle (QjoDeletePointerHandle) API</a></div>
|
||
|
|
<div><a href="../cl/dspjrn.htm">Display Journal (DSPJRN) command</a></div>
|
||
|
|
<div><a href="../apis/getpthff.htm">Get Path Name of Object from Its File ID (Qp0lGetPathFromFileID()) API</a></div>
|
||
|
|
<div><a href="../cl/rcvjrne.htm">Receive Journal Entry (RCVJRNE) command</a></div>
|
||
|
|
<div><a href="../cl/rtvjrne.htm">Retrieve Journal Entry (RTVJRNE) command</a></div>
|
||
|
|
<div><a href="../apis/QJORJRNE.htm">Retrieve Journal Entries (QjoRetrieveJournalEntries) API</a></div>
|
||
|
|
<div><a href="../cl/rmvjrnchg.htm">Remove Journaled Changes (RMVJRNCHG) command</a></div>
|
||
|
|
<div><img src="./delta.gif" alt="Start of change" /><a href="../apis/qdbrplay.htm">Replay Database Operation (QDBRPLAY) API</a><img src="./deltaend.gif" alt="End of change" /></div>
|
||
|
|
<div><a href="../cl/sndjrne.htm">Send Journal Entry (SNDJRNE) command</a></div>
|
||
|
|
<div><a href="../apis/QJOSJRNE.htm">Send Journal Entry (QJOSJRNE) API</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|