105 lines
6.7 KiB
HTML
105 lines
6.7 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="reference" />
|
|
<meta name="DC.Title" content="Journal objects and save journal receivers" />
|
|
<meta name="abstract" content="If your save operations for database files take too long because your files are large, saving changed objects might not help you." />
|
|
<meta name="description" content="If your save operations for database files take too long because your files are large, saving changed objects might not help you." />
|
|
<meta name="DC.Relation" scheme="URI" content="rzaj1mediumstrat.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="../rzaki/rzakikickoff.htm" />
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 2000, 2006" />
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 2000, 2006" />
|
|
<meta name="DC.Format" content="XHTML" />
|
|
<meta name="DC.Identifier" content="rzaj1jrnldb" />
|
|
<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 objects and save journal receivers</title>
|
|
</head>
|
|
<body id="rzaj1jrnldb"><a name="rzaj1jrnldb"><!-- --></a>
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|
<h1 class="topictitle1">Journal objects and save journal receivers</h1>
|
|
<div><p>If your save operations for database files take too long because
|
|
your files are large, saving changed objects might not help you.</p>
|
|
<div class="section"><p>If you have a file member with 100 000 records and 1 record changes,
|
|
the SAVCHGOBJ command saves the entire file member. In this situation, journaling
|
|
your database files and saving journal receivers regularly might be a better
|
|
solution, even though recovery is more complex.</p>
|
|
<p>A similar principle
|
|
applies to integrated file system objects and data areas. If your save operations
|
|
for integrated file system objects and data areas are taking too long, you
|
|
can choose to journal the objects to make your save operations more efficient.
|
|
Saving journal receivers might be a better option.</p>
|
|
<p>When you journal
|
|
objects, the system writes a copy of every change in the object to a journal
|
|
receiver. When you save a journal receiver, you are saving only the changed
|
|
portions of the object, not the entire object.</p>
|
|
<p>If you journal your objects
|
|
and have a batch work load that varies, your save strategy might look like
|
|
this:</p>
|
|
|
|
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" width="100%" frame="void" border="0" rules="none"><caption>Table 1. Example save strategy</caption><thead align="left"><tr><th align="left" valign="bottom" width="30.246913580246915%" id="d0e33">Day</th>
|
|
<th align="left" valign="bottom" width="29.938271604938272%" id="d0e35">Batch workload</th>
|
|
<th align="left" valign="bottom" width="39.81481481481482%" id="d0e37">Save operation</th>
|
|
</tr>
|
|
</thead>
|
|
<tbody><tr><td align="left" valign="top" width="30.246913580246915%" headers="d0e33 ">Friday night</td>
|
|
<td align="left" valign="top" width="29.938271604938272%" headers="d0e35 ">Light</td>
|
|
<td align="left" valign="top" width="39.81481481481482%" headers="d0e37 ">Save menu option 21</td>
|
|
</tr>
|
|
<tr><td align="left" valign="top" width="30.246913580246915%" headers="d0e33 ">Monday night</td>
|
|
<td align="left" valign="top" width="29.938271604938272%" headers="d0e35 ">Heavy</td>
|
|
<td align="left" valign="top" width="39.81481481481482%" headers="d0e37 ">Save journal receivers</td>
|
|
</tr>
|
|
<tr><td align="left" valign="top" width="30.246913580246915%" headers="d0e33 ">Tuesday night</td>
|
|
<td align="left" valign="top" width="29.938271604938272%" headers="d0e35 ">Light</td>
|
|
<td align="left" valign="top" width="39.81481481481482%" headers="d0e37 ">Save menu option 23</td>
|
|
</tr>
|
|
<tr><td align="left" valign="top" width="30.246913580246915%" headers="d0e33 ">Wednesday night</td>
|
|
<td align="left" valign="top" width="29.938271604938272%" headers="d0e35 ">Heavy</td>
|
|
<td align="left" valign="top" width="39.81481481481482%" headers="d0e37 ">Save journal receivers</td>
|
|
</tr>
|
|
<tr><td align="left" valign="top" width="30.246913580246915%" headers="d0e33 ">Thursday night</td>
|
|
<td align="left" valign="top" width="29.938271604938272%" headers="d0e35 ">Heavy</td>
|
|
<td align="left" valign="top" width="39.81481481481482%" headers="d0e37 ">Save journal receivers</td>
|
|
</tr>
|
|
<tr><td align="left" valign="top" width="30.246913580246915%" headers="d0e33 ">Friday night</td>
|
|
<td align="left" valign="top" width="29.938271604938272%" headers="d0e35 ">Light</td>
|
|
<td align="left" valign="top" width="39.81481481481482%" headers="d0e37 ">Save menu option 21</td>
|
|
</tr>
|
|
</tbody>
|
|
</table>
|
|
</div>
|
|
<div class="note"><span class="notetitle">Notes:</span> <ol><li>To take advantage of the protection that journaling provides, you should
|
|
detach and save journal receivers regularly. How often you save them depends
|
|
on the number of journaled changes that occur. Saving journal receivers several
|
|
times during the day might be appropriate for you. How you save journal receivers
|
|
depends on whether they are in a separate library. You might use the Save
|
|
Library (SAVLIB) command or the Save Object (SAVOBJ) command.</li>
|
|
<li>You must save new objects before you can apply journal entries to the
|
|
object. If your applications regularly add new objects, you should consider
|
|
using the SAVCHGOBJ strategy either by itself or in combination with journaling.</li>
|
|
</ol>
|
|
</div>
|
|
</div>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaj1mediumstrat.htm" title="You have a medium save window, which means that you have a 4- to 6-hour block of time available daily with no system activity. Use this strategy if you find that you do not have a long-enough save window to use a simple save strategy.">Medium save strategy</a></div>
|
|
</div>
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
|
<div><a href="../rzaki/rzakikickoff.htm">Journal management</a></div>
|
|
</div>
|
|
</div>
|
|
</body>
|
|
</html> |