123 lines
7.5 KiB
HTML
123 lines
7.5 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="Use existing access paths" />
|
||
|
|
<meta name="abstract" content="When two or more files are based on the same physical files and the same key fields in the same order, they automatically share the same keyed sequence access path. When access paths are shared, the amount of system activity required to maintain access paths and the amount of auxiliary storage used by the files is reduced." />
|
||
|
|
<meta name="description" content="When two or more files are based on the same physical files and the same key fields in the same order, they automatically share the same keyed sequence access path. When access paths are shared, the amount of system activity required to maintain access paths and the amount of auxiliary storage used by the files is reduced." />
|
||
|
|
<meta name="DC.subject" content="existing access path, using, access path, sharing" />
|
||
|
|
<meta name="keywords" content="existing access path, using, access path, sharing" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbafodaplf.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbafoiapse.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbafofifoo.htm" />
|
||
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 1998, 2006" />
|
||
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 1998, 2006" />
|
||
|
|
<meta name="DC.Format" content="XHTML" />
|
||
|
|
<meta name="DC.Identifier" content="rbafoshrap" />
|
||
|
|
<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>Use existing access paths</title>
|
||
|
|
</head>
|
||
|
|
<body id="rbafoshrap"><a name="rbafoshrap"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Use existing access paths</h1>
|
||
|
|
<div><p>When two or more files are based on the same physical files and
|
||
|
|
the same key fields in the same order, they automatically share the same keyed
|
||
|
|
sequence access path. When access paths are shared, the amount of system activity
|
||
|
|
required to maintain access paths and the amount of auxiliary storage used
|
||
|
|
by the files is reduced.</p>
|
||
|
|
<div class="p">When a logical file with a keyed sequence access path is created, the system
|
||
|
|
always tries to share an existing access path. For access path sharing to
|
||
|
|
occur, an access path must exist on the system that satisfies the following
|
||
|
|
conditions: <ul><li class="liexpand">The logical file member to be added must be based on the same physical
|
||
|
|
file members that the existing access path is based on.</li>
|
||
|
|
<li class="liexpand">The length, data type, and number of decimal positions specified for each
|
||
|
|
key field must be identical in both the new file and the existing file.</li>
|
||
|
|
<li class="liexpand">If the FIFO, LIFO, or FCFO keyword is not specified, the new file can
|
||
|
|
have fewer key fields than the existing access paths. That is, a new logical
|
||
|
|
file can share an existing access path if the beginning part of the key is
|
||
|
|
identical. However, when a file shares a partial set of keys from an existing
|
||
|
|
access path, any record updates made to fields that are part of the set of
|
||
|
|
keys for the shared access path might change the record position in that access
|
||
|
|
path. </li>
|
||
|
|
<li class="liexpand">The attributes of the access path (such as UNIQUE, LIFO, FIFO, or FCFO)
|
||
|
|
and the attributes of the key fields (such as DESCEND, ABSVAL, UNSIGNED, and
|
||
|
|
SIGNED) must be identical. <div class="p">Exceptions: <ol><li>A FIFO access path can share an access path in which the UNIQUE keyword
|
||
|
|
is specified if all the other requirements for access path sharing are met.</li>
|
||
|
|
<li>A UNIQUE access path can share a FIFO access path that needs to be rebuilt
|
||
|
|
(for example, has *REBLD maintenance specified), if all the other requirements
|
||
|
|
for access path sharing are met.</li>
|
||
|
|
</ol>
|
||
|
|
</div>
|
||
|
|
</li>
|
||
|
|
<li class="liexpand">If the new logical file has select/omit specifications, they must be identical
|
||
|
|
to the select/omit specifications of the existing access path. However, if
|
||
|
|
the new logical file specifies DYNSLT, it can share an existing access path
|
||
|
|
if the existing access path has either: <ul><li>The dynamic select (DYNSLT) keyword specified</li>
|
||
|
|
<li>No select/omit keywords specified</li>
|
||
|
|
</ul>
|
||
|
|
</li>
|
||
|
|
<li class="liexpand">The alternative collating sequence (ALTSEQ keyword) and the translation
|
||
|
|
table (TRNTBL keyword) of the new logical file member, if any, must be identical
|
||
|
|
to the alternative collating sequence and translation table of the existing
|
||
|
|
access path.</li>
|
||
|
|
</ul>
|
||
|
|
<div class="note"><span class="notetitle">Note:</span> Logical files that contain concatenated or substring fields cannot
|
||
|
|
share access paths with physical files.</div>
|
||
|
|
</div>
|
||
|
|
<div class="p">The
|
||
|
|
owner of any access path is the logical file member that originally created
|
||
|
|
the access path. For a shared access path, if the logical member owning the
|
||
|
|
access path is deleted, the first member to share the access path becomes
|
||
|
|
the new owner. The FRCACCPTH, MAINT, and RECOVER parameters on the Create
|
||
|
|
Logical File (CRTLF) command need not match the same parameters on an existing
|
||
|
|
access path for that access path to be shared. When an access path is shared
|
||
|
|
by several logical file members, and the FRCACCPTH, MAINT, and RECOVER parameters
|
||
|
|
are not identical, the system maintains the access path by the most restrictive
|
||
|
|
value for each of the parameters specified by the sharing members. The following
|
||
|
|
list illustrates how this occurs:<ul><li>MBRA specifies:<pre>FRCACCPTH (*NO)
|
||
|
|
MAINT (*IMMED)
|
||
|
|
RECOVER (*AFTIPL)</pre>
|
||
|
|
</li>
|
||
|
|
<li>MBRB specifies:</li>
|
||
|
|
<li><pre>FRCACCPTH (*YES)
|
||
|
|
MAINT (*DLY)
|
||
|
|
RECOVER (*NO)</pre>
|
||
|
|
</li>
|
||
|
|
<li>System does:<pre>FRCACCPTH (*YES)
|
||
|
|
MAINT (*IMMED)
|
||
|
|
RECOVER (*AFTIPL)</pre>
|
||
|
|
</li>
|
||
|
|
</ul>
|
||
|
|
</div>
|
||
|
|
<p>Access path sharing does not depend on sharing between members; therefore,
|
||
|
|
it does not restrict the order in which members can be deleted.</p>
|
||
|
|
<p>The Display File Description (DSPFD) and Display Database Relations (DSPDBR)
|
||
|
|
commands show access path sharing relationships.</p>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<ul class="ullinks">
|
||
|
|
<li class="ulchildlink"><strong><a href="rbafoiapse.htm">Example: Implicitly shared access paths</a></strong><br />
|
||
|
|
This example shows how to implicitly share access path.</li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbafodaplf.htm" title="Use one of the ways to describe access paths for logical files.">Describe access paths for logical files</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
||
|
|
<div><a href="rbafofifoo.htm" title="If you do not specify the UNIQUE keyword in data description specifications (DDS), you can specify how the system stores records with duplicate key values, if duplicate key values occur.">Arrange duplicate keys</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|