87 lines
6.6 KiB
HTML
87 lines
6.6 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="Object assignment to journals" />
|
||
|
|
<meta name="abstract" content="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." />
|
||
|
|
<meta name="description" content="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." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakiplnjrnsu.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakidiskpoolrcv.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakijkldev.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="rzakiobjassnjrn" />
|
||
|
|
<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>Object assignment to journals</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzakiobjassnjrn"><a name="rzakiobjassnjrn"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Object assignment to journals</h1>
|
||
|
|
<div><p>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.</p>
|
||
|
|
<p>When deciding how many journals to use and how to assign objects to journals,
|
||
|
|
consider the following:</p>
|
||
|
|
<ul><li>Using one journal (and journal receiver) is the simplest method for managing
|
||
|
|
both daily operations and recovery.</li>
|
||
|
|
<li><img src="./delta.gif" alt="Start of change" />There is a limit of 10,000,000 objects that can
|
||
|
|
be journaled to a single journal.<img src="./deltaend.gif" alt="End of change" /></li>
|
||
|
|
<li>If using a single journal receiver causes a performance bottleneck, you
|
||
|
|
can alleviate this by placing the journal receiver in a separate disk pool
|
||
|
|
from the objects that you are journaling.</li>
|
||
|
|
<li>To simplify recovery, assign objects that are used together in the same
|
||
|
|
application to the same journal.</li>
|
||
|
|
<li>If you are journaling database files, all the physical files underlying
|
||
|
|
a logical file must be assigned to the same journal.</li>
|
||
|
|
<li>Files opened under the same commitment definition within a job can be
|
||
|
|
journaled to different journals. In commitment control, each journal is considered
|
||
|
|
a local location.</li>
|
||
|
|
<li>If your major applications have completely separate objects and backup
|
||
|
|
schedules, separate journals for the applications may simplify operating procedures
|
||
|
|
and recovery.</li>
|
||
|
|
<li>If you journal different objects for different reasons; such as recovery,
|
||
|
|
auditing, or transferring transactions to another system; you may want to
|
||
|
|
separate these functions into separate journals. However, you can assign an
|
||
|
|
object to only one journal.</li>
|
||
|
|
<li>If the security of certain objects requires that you exclude their backup
|
||
|
|
and recovery procedures from the procedures for other objects, assign them
|
||
|
|
to a separate journal, if possible.</li>
|
||
|
|
<li>If you have basic disk pools with libraries, all objects assigned to a
|
||
|
|
journal must be in the same disk pool as the journal. The journal receiver
|
||
|
|
may be in a different disk pool. If you place a journal in a disk pool without
|
||
|
|
libraries (non library disk pool), objects being journaled must be in the
|
||
|
|
system disk pool. The journal receiver may be in either the system disk pool
|
||
|
|
or the non library disk pool with the journal. See Determine the type disk
|
||
|
|
pool in which to place journal receivers for more information about the types
|
||
|
|
of disk pools.</li>
|
||
|
|
<li>If you have independent disk pools, they must be library capable in order
|
||
|
|
to journal objects on them. You cannot journal objects on User-Defined File
|
||
|
|
System (UDFS) independent disk pools.</li>
|
||
|
|
</ul>
|
||
|
|
</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 class="relconcepts"><strong>Related concepts</strong><br />
|
||
|
|
<div><a href="rzakidiskpoolrcv.htm" title="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.">Determine the type of disk pool in which to place journal receivers</a></div>
|
||
|
|
<div><a href="rzakijkldev.htm" title="JKLDEV is JKL's development server. Though it does not require 24x7 availability, the data on it represent many person hours of work by the developers. Therefore it is important that in the event of a crash, the system be brought to a current state. Also, since it is a development server, changes to the data occur often.">JKLDEV</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|