69 lines
5.7 KiB
HTML
69 lines
5.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 management concepts" />
|
||
|
|
<meta name="abstract" content="This topic explains how journal management works, why to use it, and how it affects your system." />
|
||
|
|
<meta name="description" content="This topic explains how journal management works, why to use it, and how it affects your system." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakijrnkickoff.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakireasons.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakihowwrks.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakijrnentryconcepts.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakijrnsysperform.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakijrnswa.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="rzakiconcepts" />
|
||
|
|
<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 management concepts</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzakiconcepts"><a name="rzakiconcepts"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Journal management concepts</h1>
|
||
|
|
<div><p>This topic explains how journal management works, why to use it,
|
||
|
|
and how it affects your system.</p>
|
||
|
|
<p>Journal management enables you to recover the changes to an object that
|
||
|
|
have occurred since the object was last saved. You can also use journal management
|
||
|
|
to provide an audit trail or to help replicate an object. You use a journal
|
||
|
|
to define what objects you want to protect with journal management. The system
|
||
|
|
keeps a record of changes you make to objects that are journaled and of other
|
||
|
|
events that occur on the system.</p>
|
||
|
|
<p>This topic provides information about how journals work, information about
|
||
|
|
journal entries, and how journals affect system performance.</p>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<ul class="ullinks">
|
||
|
|
<li class="ulchildlink"><strong><a href="rzakireasons.htm">Benefits of journal management</a></strong><br />
|
||
|
|
The primary benefit of journal management is that it enables you to recover the changes to an object that have occurred since the object was last saved. This ability is especially useful if you have an unscheduled outage such as a power failure.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzakihowwrks.htm">How journal management works</a></strong><br />
|
||
|
|
Use journal management to create an object called a <span class="uicontrol">journal</span>.
|
||
|
|
Use a journal to define which objects you want to protect. You can have more
|
||
|
|
than one journal on your system. A journal can define protection for more
|
||
|
|
than one object.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzakijrnentryconcepts.htm">Journal entries</a></strong><br />
|
||
|
|
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.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzakijrnsysperform.htm">Journal management and system performance</a></strong><br />
|
||
|
|
Journal management prevents transactions from being lost if your system ends abnormally or has to be recovered. To do this, journal management writes changes to journaled objects immediately to the journal receiver in auxiliary storage. This increases the disk activity on your system and can have a noticeable affect on system performance. Journaling also increases the overhead associated with opening objects and closing objects.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzakijrnswa.htm">Journal management with the save-while-active function</a></strong><br />
|
||
|
|
Journaling can help you with recovery if you use the save-while-active function in your backup strategy. If you plan to save an application without ending it for checkpoint processing, consider journaling all of the objects associated with the application. After the save operation is complete, save all of the journal receivers for the objects you are saving.</li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzakijrnkickoff.htm" title="Use local journal management to recover the changes to an object that have occurred since the object was last saved, as an audit trail, or to help replicate an object. Setting up journaling locally is a prerequisite for other iSeries functions such as Remote journal management and Commitment control. Use this information to set up, manage, and troubleshoot journaling on a local server.">Local journal management</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|