ibm-information-center/dist/eclipse/plugins/i5OS.ic.rzaki_5.4.0.1/rzakijrnobjlmt.htm

79 lines
5.5 KiB
HTML
Raw Normal View History

2024-04-02 14:02:31 +00:00
<?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 object limit" />
<meta name="abstract" content="The journal object limit (JRNOBJLMT) parameter allows you to set the maximum number of objects that will be allowed to be journaled to the journal." />
<meta name="description" content="The journal object limit (JRNOBJLMT) parameter allows you to set the maximum number of objects that will be allowed to be journaled to the journal." />
<meta name="DC.Relation" scheme="URI" content="rzakiplnjrnsu.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="journalobjectlimit" />
<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 object limit</title>
</head>
<body id="journalobjectlimit"><a name="journalobjectlimit"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">Journal object limit</h1>
<div><p>The journal object limit (JRNOBJLMT) parameter allows you to set
the maximum number of objects that will be allowed to be journaled to the
journal. </p>
<p><img src="./delta.gif" alt="Start of change" />The journaled object limit is the maximum number of objects
that can be journaled to one journal. You can set the journal object limit
to either 250,000 or 10,000,000. Use the Journal Object Limit (JRNOBJLMT)
parameter on the Create Journal (CRTJRN) or Change Journal (CHGJRN) command
to set the maximum number of journaled objects.<img src="./deltaend.gif" alt="End of change" /></p>
<p><img src="./delta.gif" alt="Start of change" />The value *MAX10M can only be specified for the Journal Object
Limit (JRNOBJLMT) parameter if the Receiver Size Option (RCVSIZOPT) parameter
has one of the receiver maximum values specified, or if RCVSIZOPT is *SYSDFT.<img src="./deltaend.gif" alt="End of change" /></p>
<p>Some factors to consider in determining the journal object limit are: </p>
<ul><li>Number of objects that would be actively changing at any given time</li>
<li><img src="./delta.gif" alt="Start of change" />The impact journaling has on the performance of your system<img src="./deltaend.gif" alt="End of change" /></li>
<li>Importance in being able to get some parallelism at IPL, run-time, hot-site
apply, and high-availability (HA) replay time</li>
<li>Complexity of managing your journal environment with multiple journals</li>
<li>Complexity of your hot-site recovery procedures if you have dependencies
between objects journaled to different journals </li>
<li>Number of objects you may need to journal in the future</li>
<li><img src="./delta.gif" alt="Start of change" />Increasing the quantity of objects associated with a single
journal may increase your IPL time, independent ASP vary on time, or disaster
recovery time. As a general rule, if the number of actively changing objects
is likely to be greater than 5,000, consider journaling some of these objects
to a separate journal. The larger the number of actively changing objects
for a given journal at system termination, the longer it will take to recover
the journal at IPL or vary on of an independent ASP.<img src="./deltaend.gif" alt="End of change" /></li>
</ul>
<p><strong>*MAX250K</strong></p>
<p>The maximum number of objects that can be journaled to one journal is 250,000.
This is the default value.</p>
<p><strong>*MAX10M</strong></p>
<p>The maximum number of objects that can be journaled to a single journal
is 10,000,000. A journal employing this attribute cannot be saved and restored
to any releases prior to V5R4 nor can it be replicated to any remote journals
on any systems prior to V5R4.</p>
<div class="note"><span class="notetitle">Note:</span> Once you have chosen the *MAX10M option, you cannot switch
back to the *MAX250K value.</div>
<p><img src="./delta.gif" alt="Start of change" />If the number of currently journaled objects is greater than
the maximum number of journaled objects, a start journal request will fail.<img src="./deltaend.gif" alt="End of change" /></p>
<div class="note"><span class="notetitle">Note:</span> A new receiver must be attached at the same time as this value is changed. </div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzakiplnjrnsu.htm" title="The following topics provide information to plan configuration for journals. They provide information about each option that you can select for journal.">Plan setup for journals</a></div>
</div>
</div>
</body>
</html>