49 lines
3.4 KiB
HTML
49 lines
3.4 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="Access path description" />
|
||
|
|
<meta name="abstract" content="When you describe a database file to the system, you describe the two major parts of the file: the record format and the access path. An access path describes the order in which records are to be retrieved. So when you describe an access path, you describe whether it will be a keyed sequence or arrival sequence access path." />
|
||
|
|
<meta name="description" content="When you describe a database file to the system, you describe the two major parts of the file: the record format and the access path. An access path describes the order in which records are to be retrieved. So when you describe an access path, you describe whether it will be a keyed sequence or arrival sequence access path." />
|
||
|
|
<meta name="DC.subject" content="describing, access paths, overview, access path, index" />
|
||
|
|
<meta name="keywords" content="describing, access paths, overview, access path, index" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbafodeffi.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbafoapath.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="rbafoapd" />
|
||
|
|
<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>Access path description</title>
|
||
|
|
</head>
|
||
|
|
<body id="rbafoapd"><a name="rbafoapd"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Access path description</h1>
|
||
|
|
<div><p>When you describe a database file to the system, you describe the
|
||
|
|
two major parts of the file: the record format and the access
|
||
|
|
path. An access path describes the order in which records are to be retrieved.
|
||
|
|
So when you describe an access path, you describe whether it will be a keyed
|
||
|
|
sequence or arrival sequence access path. </p>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbafodeffi.htm" title="This topic discusses the ways to describe records in database files.">How database files are described</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
||
|
|
<div><a href="rbafoapath.htm" title="These topics discuss the different ways of describing access paths for database files.">Describe access paths for database files</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|