94 lines
9.1 KiB
HTML
94 lines
9.1 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 setup for journals" />
|
||
|
|
<meta name="abstract" content="The following topics provide information to plan configuration for journals. They provide information about each option that you can select for journal." />
|
||
|
|
<meta name="description" content="The following topics provide information to plan configuration for journals. They provide information about each option that you can select for journal." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakiplnjrn.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakidiskassign.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakijrnlib.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakinamejrn.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakiassociatejrn.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakijrnmssgque.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakimanorsysmng.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakiautodelete.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakisizeoptions.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakijrnobjlmt.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakiminendta.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakiadjrcryratio.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakiintrusion.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakijrncache.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakiobjassnjrn.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakisetupjrngs.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="rzakiplnjrnsu" />
|
||
|
|
<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 setup for journals</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzakiplnjrnsu"><a name="rzakiplnjrnsu"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Plan setup for journals</h1>
|
||
|
|
<div><p>The following topics provide information to plan configuration
|
||
|
|
for journals. They provide information about each option that you can select
|
||
|
|
for journal.</p>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<ul class="ullinks">
|
||
|
|
<li class="ulchildlink"><strong><a href="rzakidiskassign.htm">Disk pool assignment for journals</a></strong><br />
|
||
|
|
If you want to place the journal in a library basic disk pool, you must first create the library for the journal in the disk pool. If you use a library basic disk pool, the journal and all the objects you are journaling to it must be in the same library basic disk pool.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzakijrnlib.htm">Library assignment for journals</a></strong><br />
|
||
|
|
When you create a journal, you specify a qualified name that includes the library for the journal. The library must exist before you create the journal.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzakinamejrn.htm">Naming conventions for journals</a></strong><br />
|
||
|
|
When you create a journal with iSeries™ Navigator or the Create Journal
|
||
|
|
(CRTJRN) command, you assign a name to it. If you plan to have more than one
|
||
|
|
journal on your system, use a naming convention that links each journal with
|
||
|
|
its associated receiver.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzakiassociatejrn.htm">Journal and journal receiver association</a></strong><br />
|
||
|
|
When you create a journal, you must specify the name of the journal receiver to be attached to it. If you are using the Create Journal (CRTJRN) command to create the journal, the journal receiver must exist before you can create the journal.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzakijrnmssgque.htm">Journal message queue</a></strong><br />
|
||
|
|
When you create or change a journal, you can specify where the system sends messages that are associated with the journal. In addition, you can create a program to monitor this message queue and handle any messages associated with the journal. The system also sends messages that are related to the remote journal function to this message queue.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzakimanorsysmng.htm">Manual versus system journal-receiver management</a></strong><br />
|
||
|
|
When you create a journal with iSeries Navigator or the Create Journal (CRTJRN) command, you can select to have either system managed or user managed journal receivers.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzakiautodelete.htm">Automatic deletion of journal receivers</a></strong><br />
|
||
|
|
If you choose system journal receiver management, you can also have the system delete journal receivers that are no longer needed for recovery. You can only specify this if you are using system journal receiver management.</li>
|
||
|
|
<li class="ulchildlink"><img src="./delta.gif" alt="Start of change" /><strong><a href="rzakisizeoptions.htm">Receiver size options for journals</a></strong><img src="./deltaend.gif" alt="End of change" /><br />
|
||
|
|
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.</li>
|
||
|
|
<li class="ulchildlink"><img src="./delta.gif" alt="Start of change" /><strong><a href="rzakijrnobjlmt.htm">Journal object limit</a></strong><img src="./deltaend.gif" alt="End of change" /><br />
|
||
|
|
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.</li>
|
||
|
|
<li class="ulchildlink"><img src="./delta.gif" alt="Start of change" /><strong><a href="rzakiminendta.htm">Minimized entry-specific data for journal entries</a></strong><img src="./deltaend.gif" alt="End of change" /><br />
|
||
|
|
On the Create Journal (CRTJRN) and Change Journal (CHGJRN) commands, you can specify to allow for the deposit of minimized journal entries. This will decrease the size of your journal entries.</li>
|
||
|
|
<li class="ulchildlink"><img src="./delta.gif" alt="Start of change" /><strong><a href="rzakiadjrcryratio.htm">Customize the journal recovery count</a></strong><img src="./deltaend.gif" alt="End of change" /><br />
|
||
|
|
Use the Journal Recovery Count (JRNRCYCNT) parameter in the CHGJRN command to set the journal recovery ratio for each journal.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzakiintrusion.htm">Fixed-length options for journal entries</a></strong><br />
|
||
|
|
You can use the Fixed Length Data (FIXLENDTA) parameter of Create Journal (CRTJRN) and Change Journal (CHGJRN) commands to audit security related activity for journaled objects on your system.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzakijrncache.htm">Journal cache</a></strong><br />
|
||
|
|
Journal caching is separately chargeable feature with which you can specify that the system cache journal entries in main storage, before writing them to disk. Journal caching is option 42 of
|
||
|
|
the i5/OS<sup>®</sup> operating system.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzakiobjassnjrn.htm">Object assignment to journals</a></strong><br />
|
||
|
|
You can use one journal to manage all the objects you are journaling. Or, you can set up several journals if groups of objects have different backup and recovery requirements. Every journal has a single attached receiver. All journal entries for all objects being managed by the journal are written to the same journal receiver.</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="reltasks"><strong>Related tasks</strong><br />
|
||
|
|
<div><a href="rzakisetupjrngs.htm" title="Provides instructions on how to set up journals and journal receivers.">Set up journaling</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|