82 lines
4.9 KiB
HTML
82 lines
4.9 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="task" />
|
||
|
|
<meta name="DC.Title" content="Journal access paths" />
|
||
|
|
<meta name="abstract" content="After you have started journaling for physical files, you can set up explicit journaling of access paths." />
|
||
|
|
<meta name="description" content="After you have started journaling for physical files, you can set up explicit journaling of access paths." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakistrjrnl.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../cl/strjrnap.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakijrnap.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="rzakistrjrnap" />
|
||
|
|
<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 access paths</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzakistrjrnap"><a name="rzakistrjrnap"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Journal access paths</h1>
|
||
|
|
<div><p>After you have started journaling for physical files, you can set
|
||
|
|
up explicit journaling of access paths.</p>
|
||
|
|
<div class="section"><p>You can use the Start Journal Access Path (STRJRNAP) command to
|
||
|
|
start journaling access paths owned by physical files or logical files. When
|
||
|
|
you start journaling access paths for a physical file, the system journals
|
||
|
|
any of these, if they exist:</p>
|
||
|
|
<ul><li>Keyed access paths</li>
|
||
|
|
<li>Access paths for primary key constraints</li>
|
||
|
|
<li>Access paths for unique constraints</li>
|
||
|
|
<li>Access paths for referential constraints</li>
|
||
|
|
<li><img src="./delta.gif" alt="Start of change" />Encoded vector access paths<img src="./deltaend.gif" alt="End of change" /></li>
|
||
|
|
<li><img src="./delta.gif" alt="Start of change" />Many access paths with sort sequence tables <img src="./deltaend.gif" alt="End of change" /></li>
|
||
|
|
</ul>
|
||
|
|
<p><img src="./delta.gif" alt="Start of change" />Some access paths that use an international
|
||
|
|
component for Unicode (ICU) sort sequence table may be too complex to be journaled.<img src="./deltaend.gif" alt="End of change" /></p>
|
||
|
|
<p>All
|
||
|
|
underlying physical files must be journaled to the same journal before you
|
||
|
|
can start journaling for an access path. The entries created when you journal
|
||
|
|
an access path are used to recover the access path after the system ends abnormally.
|
||
|
|
They are not used when you apply or remove journal entries. You can specify
|
||
|
|
RCVSIZOPT(*RMVINTENT) for the journal to have the system remove these entries
|
||
|
|
when they are no longer needed for recovery. This reduces the disk storage
|
||
|
|
requirements for the journal receiver.</p>
|
||
|
|
<p>You cannot start journaling for
|
||
|
|
an access path that is in use. The STRJRNAP command must obtain an *EXCL lock
|
||
|
|
on the logical file.</p>
|
||
|
|
<p>The recommended procedure for starting access path
|
||
|
|
journaling is as follows:</p>
|
||
|
|
</div>
|
||
|
|
<ol><li><span>Use the STRJRNAP command to start journaling the access path.</span></li>
|
||
|
|
<li><span>Save all the underlying physical files, specifying ACCPTH(*YES).</span></li>
|
||
|
|
</ol>
|
||
|
|
<div class="section"><p>If you have target recovery times for access paths set up on your
|
||
|
|
system, you may not need to set up explicit journaling for access paths. See
|
||
|
|
Reasons to journal access paths for more information.</p>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzakistrjrnl.htm" title="This topic provides information about how to start journaling for all object types.">Start journaling</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
||
|
|
<div><a href="rzakijrnap.htm" title="If you journal access paths, the system can use the journal entries to recover access paths instead of rebuilding them completely.">Reasons to journal access paths</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relref"><strong>Related reference</strong><br />
|
||
|
|
<div><a href="../cl/strjrnap.htm">Start Journal Access Path (STRJRNAP) command</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|