88 lines
8.3 KiB
HTML
88 lines
8.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="Plan for journal use of auxiliary storage" />
|
||
<meta name="abstract" content="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." />
|
||
<meta name="description" content="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." />
|
||
<meta name="DC.Relation" scheme="URI" content="rzakiplnjrn.htm" />
|
||
<meta name="DC.Relation" scheme="URI" content="rzakidiskarm.htm" />
|
||
<meta name="DC.Relation" scheme="URI" content="rzakibigrecvr.htm" />
|
||
<meta name="DC.Relation" scheme="URI" content="rzakiestimatercv.htm" />
|
||
<meta name="DC.Relation" scheme="URI" content="rzakisizecalc.htm" />
|
||
<meta name="DC.Relation" scheme="URI" content="rzakimanualestm.htm" />
|
||
<meta name="DC.Relation" scheme="URI" content="rzakireducesize.htm" />
|
||
<meta name="DC.Relation" scheme="URI" content="rzakidiskpoolrcv.htm" />
|
||
<meta name="DC.Relation" scheme="URI" content="rzakiiasp.htm" />
|
||
<meta name="DC.Relation" scheme="URI" content="rzakisizeoptions.htm" />
|
||
<meta name="DC.Relation" scheme="URI" content="rzakithreshold.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="rzakiplnuseaux" />
|
||
<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 use of auxiliary storage</title>
|
||
</head>
|
||
<body id="rzakiplnuseaux"><a name="rzakiplnuseaux"><!-- --></a>
|
||
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
<h1 class="topictitle1">Plan for journal use of auxiliary storage</h1>
|
||
<div><p>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.</p>
|
||
<p>The maximum size for a single journal receiver varies. It depends on how the system allocates the journal receiver across multiple disk arms. The maximum size ranges from approximately 1.9 GB to 1.0
|
||
TB depending on what value you specified for the associated journal's receiver size option.</p>
|
||
<p>To avoid possible problems with a journal receiver exceeding the maximum size allowed on the system, specify a threshold for the receiver of no more than 900 000 000 KB if you specified
|
||
a journal receiver maximum-size option for the associated journal. Otherwise, specify a threshold of no more than 1 441 000 KB.</p>
|
||
<p>The following topics provide more information about how journal management affects auxiliary storage:</p>
|
||
<ul><li>Functions that increase the journal receiver size</li>
|
||
<li>Methods to estimate the size of a journal receiver</li>
|
||
<li>Journal receiver calculator</li>
|
||
<li>Methods to reduce the storage that journal receivers use</li>
|
||
<li>Determine the type of disk pool in which to place journal receivers</li>
|
||
<li>Journals and independent disk pools</li>
|
||
</ul>
|
||
</div>
|
||
<div>
|
||
<ul class="ullinks">
|
||
<li class="ulchildlink"><strong><a href="rzakidiskarm.htm">Frequently asked questions about journaling and disk arm usage</a></strong><br />
|
||
Journaling affects the disk arms that store the journal receiver.</li>
|
||
<li class="ulchildlink"><strong><a href="rzakibigrecvr.htm">Functions that increase the journal receiver size</a></strong><br />
|
||
Some optional functions available with journal management can significantly increase auxiliary storage requirements.</li>
|
||
<li class="ulchildlink"><strong><a href="rzakiestimatercv.htm">Methods to estimate the size of a journal receiver</a></strong><br />
|
||
You can use the methods below to estimate the effect a journal receiver will have on auxiliary storage.</li>
|
||
<li class="ulchildlink"><strong><a href="rzakisizecalc.htm">Journal receiver calculator</a></strong><br />
|
||
Use the journal receiver calculator to estimate the size of your journal receiver.</li>
|
||
<li class="ulchildlink"><strong><a href="rzakimanualestm.htm">Estimate the size of the journal receiver manually</a></strong><br />
|
||
Use this procedure to estimate the size of your journal receiver.</li>
|
||
<li class="ulchildlink"><strong><a href="rzakireducesize.htm">Methods to reduce the storage that journal receivers use</a></strong><br />
|
||
Reduce the size of journal entries by methods such as journaling
|
||
after-images only, or specifying certain journaling options including the
|
||
Fixed Length Data (FIXLENDTA) option on the <span class="cmdname">Create Journal (CRTJRN)</span> and <span class="cmdname">Change
|
||
Journal (CHGJRN)</span> commands.</li>
|
||
<li class="ulchildlink"><strong><a href="rzakidiskpoolrcv.htm">Determine the type of disk pool in which to place journal receivers</a></strong><br />
|
||
Use disk pools (auxiliary storage pool) to control which objects are allocated to which groups of disk units. If you are journaling many active objects to the same journal, the journal receiver can become a performance bottleneck. One way to minimize the performance impact of journaling is to put the journal receiver in a separate disk pool. This also provides additional protection because your objects are on different disk units from the journal receiver, which contains a copy of changes to the objects.</li>
|
||
<li class="ulchildlink"><strong><a href="rzakiiasp.htm">Journal management and independent disk pools</a></strong><br />
|
||
Independent disk pools are disk pools 33 through 255. Independent disk pools can be user-defined file system (UDFS) independent disk pools or library-capable independent disk pools.</li>
|
||
</ul>
|
||
|
||
<div class="familylinks">
|
||
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzakiplnjrn.htm" title="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.">Plan for journal management</a></div>
|
||
</div>
|
||
<div class="relconcepts"><strong>Related concepts</strong><br />
|
||
<div><a href="rzakisizeoptions.htm" title="A journal receiver holds journal entries that you might use for recovery and entries that the system might use for recovery. For example, you might use record level entries, such as database record changes, and file level entries, such as the entry for opening or closing a file. Also, the system writes entries that you never see or use, such as entries for explicitly journaled access paths, for SMAPP, or for commitment control.">Receiver size options for journals</a></div>
|
||
<div><a href="rzakithreshold.htm" title="When you create a journal receiver with iSeries Navigator or the Create Journal Receiver (CRTJRNRCV) command, you specify a disk space threshold that indicates when you want the system to warn you or take action.">Threshold (disk space) for journal receivers</a></div>
|
||
</div>
|
||
</div>
|
||
</body>
|
||
</html> |