78 lines
6.1 KiB
HTML
78 lines
6.1 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 a keyed sequence access path for database files" />
|
||
|
|
<meta name="abstract" content="A keyed sequence access path for database files is based on the contents of the key fields as defined in data description specifications (DDS). This topic describes how the key fields are arranged for the file." />
|
||
|
|
<meta name="description" content="A keyed sequence access path for database files is based on the contents of the key fields as defined in data description specifications (DDS). This topic describes how the key fields are arranged for the file." />
|
||
|
|
<meta name="DC.subject" content="keyed sequence access path, definition, sequence access path, keyed, access path, keyed sequence, UNSIGNED (Unsigned) keyword, Unsigned (UNSIGNED) keyword, keyword, DDS, UNSIGNED (Unsigned), ABSVAL (Absolute Value) keyword, Absolute Value (ABSVAL) keyword, ABSVAL (Absolute Value)" />
|
||
|
|
<meta name="keywords" content="keyed sequence access path, definition, sequence access path, keyed, access path, keyed sequence, UNSIGNED (Unsigned) keyword, Unsigned (UNSIGNED) keyword, keyword, DDS, UNSIGNED (Unsigned), ABSVAL (Absolute Value) keyword, Absolute Value (ABSVAL) keyword, ABSVAL (Absolute Value)" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbafoapath.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbafoacolsq.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbafoakfssq.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbafoascdes.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbafokfield.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbafoprvdupk.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="rbafoksapa" />
|
||
|
|
<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 a keyed sequence access path for database files</title>
|
||
|
|
</head>
|
||
|
|
<body id="rbafoksapa"><a name="rbafoksapa"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Use a keyed sequence access path for database files</h1>
|
||
|
|
<div><p>A keyed sequence access path for database files is based on the
|
||
|
|
contents of the key fields as defined in data description specifications (DDS).
|
||
|
|
This topic describes how the key fields are arranged for the file. </p>
|
||
|
|
<p>This type of access path is updated whenever records are added
|
||
|
|
or deleted, or when records are updated and the contents of a key field is
|
||
|
|
changed. The keyed sequence access path is valid for both physical and logical
|
||
|
|
files. The sequence of the records in the file is defined in DDS when the
|
||
|
|
file is created and is maintained automatically by the system.</p>
|
||
|
|
<p>Key fields defined as character fields are arranged based on the sequence
|
||
|
|
defined for EBCDIC characters. Key fields defined as numeric fields are arranged
|
||
|
|
based on their algebraic values, unless the UNSIGNED (unsigned value) or ABSVAL
|
||
|
|
(absolute value) DDS keywords are specified for the field. Key fields defined
|
||
|
|
as DBCS are allowed, but are arranged only as single bytes based on their
|
||
|
|
bit representation.</p>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<ul class="ullinks">
|
||
|
|
<li class="ulchildlink"><strong><a href="rbafoacolsq.htm">Arrange key fields using an alternative collating sequence</a></strong><br />
|
||
|
|
Keyed fields defined as character fields can be arranged based either on the sequence for EBCDIC characters or on an alternative collating sequence.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rbafoakfssq.htm">Arrange key fields using the SRTSEQ parameter</a></strong><br />
|
||
|
|
You can arrange key fields containing character data according to several sorting sequences available with the SRTSEQ parameter.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rbafoascdes.htm">Arrange key fields in ascending or descending sequence</a></strong><br />
|
||
|
|
Key fields can be arranged in either ascending or descending sequence.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rbafokfield.htm">Use more than one key field</a></strong><br />
|
||
|
|
You can use more than one key field to arrange the records in a database file. The key fields do not have to use the same sequence.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rbafoprvdupk.htm">Prevent duplicate key values</a></strong><br />
|
||
|
|
DB2
|
||
|
|
Universal Database™ for iSeries™ allows records with duplicate key values
|
||
|
|
in your files. However, you might want to prevent duplicate key values in
|
||
|
|
some of your files.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rbafofifoo.htm">Arrange duplicate keys</a></strong><br />
|
||
|
|
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.</li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<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>
|
||
|
|
</body>
|
||
|
|
</html>
|