86 lines
5.7 KiB
HTML
86 lines
5.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="concept" />
|
|
<meta name="DC.Title" content="Use arrival sequence access path for database files" />
|
|
<meta name="abstract" content="The arrival sequence access path for database files is based on the order in which the records arrive and are stored in the file. This topic discusses what kind of file can use arrival sequence access path and how you can use the path to describe the file." />
|
|
<meta name="description" content="The arrival sequence access path for database files is based on the order in which the records arrive and are stored in the file. This topic discusses what kind of file can use arrival sequence access path and how you can use the path to describe the file." />
|
|
<meta name="DC.subject" content="arrival sequence access path, describing, sequence access path, arrival, access path, arrival sequence" />
|
|
<meta name="keywords" content="arrival sequence access path, describing, sequence access path, arrival, access path, arrival sequence" />
|
|
<meta name="DC.Relation" scheme="URI" content="rbafoapath.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rbaforsdlt.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rbafodldbr.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="rbafoasapa" />
|
|
<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 arrival sequence access path for database files</title>
|
|
</head>
|
|
<body id="rbafoasapa"><a name="rbafoasapa"><!-- --></a>
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|
<h1 class="topictitle1">Use arrival sequence access path for database files</h1>
|
|
<div><p>The arrival sequence access path for database files is based on
|
|
the order in which the records arrive and are stored in the file. This topic
|
|
discusses what kind of file can use arrival sequence access path and how you
|
|
can use the path to describe the file. </p>
|
|
<div class="p">For reading or updating, records can be accessed: <ul><li>Sequentially, where each record is taken from the next sequential physical
|
|
position in the file.</li>
|
|
<li>Directly by relative record number, where the record is identified by
|
|
its position from the start of the file.</li>
|
|
</ul>
|
|
</div>
|
|
<p>An externally described file has an arrival sequence access path when no
|
|
key fields are specified for the file.</p>
|
|
<div class="p">An arrival sequence access path is valid only for the following files: <ul><li>Physical files</li>
|
|
<li>Logical files in which each member of the logical file is based on only
|
|
one physical file member</li>
|
|
<li>Join logical files</li>
|
|
<li>Views</li>
|
|
</ul>
|
|
</div>
|
|
<div class="p">You can use arrival sequence access paths in the following ways: <ul><li>Arrival sequence is the only processing method that allows a program to
|
|
use the storage space previously occupied by a deleted record by placing another
|
|
record in that storage space. This method requires explicit insertion of a
|
|
record given a relative record number that you provide. Another method, in
|
|
which the system manages the space created by deleting records, is the reuse
|
|
deleted records attribute that can be specified for physical files.</li>
|
|
<li>Through your high-level
|
|
language, the Display Physical File Member (DSPPFM) command, and the Copy
|
|
File (CPYF) command, you can process a keyed sequence file in arrival sequence.
|
|
You can use this function for a physical file, a simple logical file based
|
|
on one physical file member, or a join logical file.</li>
|
|
<li>Through your high-level language, you can process a keyed sequence file
|
|
directly by relative record number. You can use this function for a physical
|
|
file, a simple logical file based on one physical file member, or a join logical
|
|
file.</li>
|
|
<li>An arrival sequence access path does not take up any additional storage
|
|
and is always saved or restored with the file. (Because the arrival sequence
|
|
access path is nothing more than the physical order of the data as it was
|
|
stored, when you save the data you save the arrival sequence access path.)</li>
|
|
</ul>
|
|
</div>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <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 class="relconcepts"><strong>Related concepts</strong><br />
|
|
<div><a href="rbaforsdlt.htm" title="Sometimes you might want to reuse deleted records for your database files. In this case, you can use the REUSEDLT parameter.">Reuse deleted records</a></div>
|
|
<div><a href="rbafodldbr.htm" title="The delete operation allows you to delete an existing database record.">Delete database records</a></div>
|
|
</div>
|
|
</div>
|
|
</body>
|
|
</html> |