63 lines
4.6 KiB
HTML
63 lines
4.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="Read when logical file shares an access path with more keys operation" />
|
|
<meta name="abstract" content="When the first-in-first-out (FIFO), last-in-first-out (LIFO), or first-changed-first-out (FCFO) keyword is not specified in the data description specifications (DDS) for a logical file, the logical file can implicitly share an access path that has more keys than the logical file being created." />
|
|
<meta name="description" content="When the first-in-first-out (FIFO), last-in-first-out (LIFO), or first-changed-first-out (FCFO) keyword is not specified in the data description specifications (DDS) for a logical file, the logical file can implicitly share an access path that has more keys than the logical file being created." />
|
|
<meta name="DC.subject" content="logical file, sharing access path, access path, sharing, key field, subset" />
|
|
<meta name="keywords" content="logical file, sharing access path, access path, sharing, key field, subset" />
|
|
<meta name="DC.Relation" scheme="URI" content="rbafordbrk.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="rbafordlfksap" />
|
|
<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>Read when logical file shares an access path with more keys operation</title>
|
|
</head>
|
|
<body id="rbafordlfksap"><a name="rbafordlfksap"><!-- --></a>
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|
<h1 class="topictitle1">Read when logical file shares an access path with more keys operation</h1>
|
|
<div><p>When the first-in-first-out (FIFO), last-in-first-out (LIFO), or
|
|
first-changed-first-out (FCFO) keyword is not specified in the data description
|
|
specifications (DDS) for a logical file, the logical file can implicitly share
|
|
an access path that has more keys than the logical file being created.</p>
|
|
<div class="p">This sharing of a partial set of keys from an existing access path can
|
|
lead to perceived problems for database read operations that use these partially
|
|
shared keyed sequence access paths. The problems might appear to be: <ul><li>Records that should be read, are never returned to your program</li>
|
|
<li>Records are returned to your program multiple times</li>
|
|
</ul>
|
|
</div>
|
|
<p>What is actually happening is that your program or another currently active
|
|
program is updating the physical file fields that are keys within the partially
|
|
shared keyed sequence access path, but that are not actual keys for the logical
|
|
file that is being used by your program (the fields being updated are beyond
|
|
the number of keys known to the logical file being used by your program).
|
|
The updating of the actual key fields for a logical file by your program or
|
|
another program has always yielded the above results. The difference with
|
|
partially shared keyed sequence access paths is that the updating of the physical
|
|
file fields that are keys beyond the number of keys known to the logical file
|
|
can cause the same consequences.</p>
|
|
<p>If these consequences caused by partially shared keyed sequence access
|
|
paths are not acceptable, the FIFO, LIFO, or FCFO keyword can be added to
|
|
the DDS for the logical file, and the logical file created again.</p>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbafordbrk.htm" title="These read operations can be used with a keyed sequence access path to get database records.">Read database records using a keyed sequence access path</a></div>
|
|
</div>
|
|
</div>
|
|
</body>
|
|
</html> |