93 lines
7.2 KiB
HTML
93 lines
7.2 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="Plan for journal management" />
|
||
|
|
<meta name="abstract" content="This topic provides you with the information you need to ensure you have enough disk space, to plan what objects to journal, and to plan which journaling options to use." />
|
||
|
|
<meta name="description" content="This topic provides you with the information you need to ensure you have enough disk space, to plan what objects to journal, and to plan which journaling options to use." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakijrnkickoff.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakiguivsgs.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakiplnobjrn.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakiplnuseaux.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakiplnrcv.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakiplnjrnsu.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakiremotekickoff.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="rzakiplnjrn" />
|
||
|
|
<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>Plan for journal management</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzakiplnjrn"><a name="rzakiplnjrn"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Plan for journal management</h1>
|
||
|
|
<div><p>This topic provides you with the information you need to ensure
|
||
|
|
you have enough disk space, to plan what objects to journal, and to plan which
|
||
|
|
journaling options to use.</p>
|
||
|
|
<p>Before you start to journal an object, you must make decisions that will
|
||
|
|
determine how you will create journals and receivers, what objects to journal
|
||
|
|
and how to journal those objects. These decisions include:</p>
|
||
|
|
<ul><li>Whether to use iSeries™ Navigator to set up your journaling environment.</li>
|
||
|
|
<li>What objects to protect with journaling.</li>
|
||
|
|
<li>Whether to journal other objects that the system does not journal.</li>
|
||
|
|
<li>Whether to combine journaling with the save-while-active function.</li>
|
||
|
|
<li>How many journals you need and which objects must be assigned to each
|
||
|
|
journal.</li>
|
||
|
|
<li>Whether to journal after-images only or both before-images and after-images.</li>
|
||
|
|
<li>Whether your application programs must write journal entries to assist
|
||
|
|
with recovery.</li>
|
||
|
|
<li>What type of disk pool in which to store your journal receiver.</li>
|
||
|
|
<li>Whether to use the remote journal function to replicate the journal entries
|
||
|
|
and receivers to one or more additional systems.</li>
|
||
|
|
<li>Whether to omit the optional open, close, or force entries for your objects.</li>
|
||
|
|
</ul>
|
||
|
|
<p>You also need to make operational decisions about journal management:</p>
|
||
|
|
<ul><li>How often must journal receivers be changed and saved?</li>
|
||
|
|
<li>How often must you save journaled objects?</li>
|
||
|
|
<li>How must journals and journal receivers be secured?</li>
|
||
|
|
</ul>
|
||
|
|
<p>Finally, you need to balance the benefits of journaling with the affect
|
||
|
|
it may have on your system performance and auxiliary storage requirements.</p>
|
||
|
|
<p>Use the following information to help you make these decisions:</p>
|
||
|
|
<div class="note"><span class="notetitle">Note:</span> The Remote journal management topic has information about remote journaling.</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<ul class="ullinks">
|
||
|
|
<li class="ulchildlink"><strong><a href="rzakiguivsgs.htm">iSeries Navigator versus the character-based interface for journaling objects</a></strong><br />
|
||
|
|
There are two environments that you can use for journal management: iSeries Navigator
|
||
|
|
and the character-based interface. iSeries Navigator provides a graphical
|
||
|
|
interface for journaling that is easy to use and does not require the use
|
||
|
|
of control language (CL) commands. The character-based interface requires
|
||
|
|
the use of CL commands or APIs, but has more functionality than iSeries Navigator.</li>
|
||
|
|
<li class="ulchildlink"><img src="./delta.gif" alt="Start of change" /><strong><a href="rzakiplnobjrn.htm">Plan which objects to journal</a></strong><img src="./deltaend.gif" alt="End of change" /><br />
|
||
|
|
When you plan which objects to journal, consider the following:</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzakiplnuseaux.htm">Plan for journal use of auxiliary storage</a></strong><br />
|
||
|
|
If you are journaling an object, journal management writes a copy of every object change to the journal receiver. It writes additional entries for object level activity, such as opening and closing the object, adding a member, or changing an object attribute. If you have a busy system and journal many objects, your journal receivers can quickly become very large.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzakiplnrcv.htm">Plan setup for journal receivers</a></strong><br />
|
||
|
|
The following topics provide information to plan configuration for journal receivers. They provide information about each option that you can select for journal receivers.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzakiplnjrnsu.htm">Plan setup for journals</a></strong><br />
|
||
|
|
The following topics provide information to plan configuration for journals. They provide information about each option that you can select for journal.</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 class="relconcepts"><strong>Related concepts</strong><br />
|
||
|
|
<div><a href="rzakiremotekickoff.htm" title="Use remote journal management to establish journals and journal receivers on a remote system that are associated with specific journals and journal receivers on a local system. Remote journal management replicates journal entries from the local system to the journals and journal receivers that are located on the remote system after they have been established.">Remote journal management</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|