245 lines
23 KiB
HTML
245 lines
23 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="reference" />
|
|
<meta name="DC.Title" content="Keyword entries for physical and logical files (positions 45 through 80)" />
|
|
<meta name="abstract" content="This topic lists valid keyword entries for describing physical and logical files. They are typed in positions 45 through 80 (functions)." />
|
|
<meta name="description" content="This topic lists valid keyword entries for describing physical and logical files. They are typed in positions 45 through 80 (functions)." />
|
|
<meta name="DC.subject" content="keyword entries for physical and logical files, logical files, keyword entries, physical files" />
|
|
<meta name="keywords" content="keyword entries for physical and logical files, logical files, keyword entries, physical files" />
|
|
<meta name="DC.Relation" scheme="URI" content="kickoff.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakbmsttdabsva.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakbmsttdalias.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakbmstlall.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakbmsttdaltse.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakbmsttdalwnu.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakbmsttdccsid.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakbmsttdcheck.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakbmsttdchkms.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakbmsttdcmp.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakbmsttdcolhd.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakbmstlcomp.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakbmstlconcat.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakbmsttddatfm.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakbmsttddatse.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakbmsttddexce.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakbmstpdft.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakbmsttddigit.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakbmstdtdynsl.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakbmsttdedtcd.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakbmsttdfcfo.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakbmsttdfifo.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakbmsttdfltpc.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakbmstlformat.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakbmsttdjdftv.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakbmsttdjdups.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakbmstljfile.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakbmsttdjfld.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakbmstlgjoin.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakbmsttdjref.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakbmsttdlifo.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakbmsttdnoalt.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakbmstlpfile.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakbmsttdrange.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakbmstpref.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakbmsttdrefac.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakbmstpreffld.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakbmsttdrefsh.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakbmsttdrenam.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakbmstsign.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakbmsttdsst.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakbmsttdtext.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakbmsttdtimfm.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakbmsttdtimse.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakbmsttdtrntb.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakbmsttduniqu.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakbmsttdunsig.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakbmsttdvalue.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakbmsttdvarle.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakbmsttdzone.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="../dds/rbafpmstsyntax.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="dbkwd.htm" />
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 2001, 2006" />
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 2001, 2006" />
|
|
<meta name="DC.Format" content="XHTML" />
|
|
<meta name="DC.Identifier" content="lfkeyw" />
|
|
<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>Keyword entries for physical and logical files (positions 45 through
|
|
80)</title>
|
|
</head>
|
|
<body id="lfkeyw"><a name="lfkeyw"><!-- --></a>
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|
<h1 class="topictitle1">Keyword entries for physical and logical files (positions 45 through
|
|
80)</h1>
|
|
<div><p>This topic lists valid keyword entries for describing physical
|
|
and logical files. They are typed in positions 45 through 80 (functions).</p>
|
|
<div class="section"><p>Most of the keywords are valid for both physical
|
|
and logical files. Some, however, are valid only for physical files, and some
|
|
are valid only for logical files. When this is the case, the restriction is
|
|
noted both in the keyword title and the text.</p>
|
|
</div>
|
|
<div class="section"><h4 class="sectiontitle">Specific restrictions</h4><div class="p">The following keywords are
|
|
valid only for simple and multiple format logical files: <ul><li>PFILE</li>
|
|
<li>REFACCPTH</li>
|
|
</ul>
|
|
</div>
|
|
<div class="p">The following keywords are valid only for join logical files: <ul><li>JDFTVAL</li>
|
|
<li>JDUPSEQ</li>
|
|
<li>JFILE</li>
|
|
<li>JFLD</li>
|
|
<li>JOIN</li>
|
|
<li>JREF</li>
|
|
</ul>
|
|
</div>
|
|
<p>When you use DDS to describe a source file (typically created
|
|
without DDS, using the CRTSRCPF command) or when a logical file is based on
|
|
a physical file to be used as a source file, you cannot use the following
|
|
keywords:</p>
|
|
|
|
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" width="100%" frame="void" border="1" rules="rows"><tbody><tr><td align="left" valign="top"><p>ABSVAL<br />
|
|
ALTSEQ<br />
|
|
DESCEND<br />
|
|
FCFO<br />
|
|
FIFO<br />
|
|
LIFO</p>
|
|
</td>
|
|
<td align="left" valign="top"><p>NOALTSEQ<br />
|
|
SIGNED<br />
|
|
UNIQUE<br />
|
|
VARLEN<br />
|
|
ZONE</p>
|
|
</td>
|
|
</tr>
|
|
</tbody>
|
|
</table>
|
|
</div>
|
|
</div>
|
|
</div>
|
|
<div>
|
|
<ul class="ullinks">
|
|
<li class="ulchildlink"><strong><a href="rzakbmsttdabsva.htm">ABSVAL (Absolute Value) keyword for physical and logical files</a></strong><br />
|
|
Use this key field level keyword to direct the operating system to ignore the sign of the field when it sequences the values associated with this numeric field. This keyword has no parameters.</li>
|
|
<li class="ulchildlink"><strong><a href="rzakbmsttdalias.htm">ALIAS (Alternative Name) keyword for physical and logical files</a></strong><br />
|
|
Use this field-level keyword to specify an alternative name for a field. When the program is compiled, the alternative name is brought into the program instead of the DDS field name.</li>
|
|
<li class="ulchildlink"><strong><a href="rzakbmstlall.htm">ALL (All) keyword—logical files only</a></strong><br />
|
|
Use this select/omit field-level keyword to specify the action to be taken after all other select/omit specifications have been processed for this logical file.</li>
|
|
<li class="ulchildlink"><strong><a href="rzakbmsttdaltse.htm">ALTSEQ (Alternative Collating Sequence) keyword for physical and logical files</a></strong><br />
|
|
Use this file-level keyword to direct the operating system to use an alternative collating sequence table when sequencing the records of a file member for retrieval, if you specified a key for this file.</li>
|
|
<li class="ulchildlink"><strong><a href="rzakbmsttdalwnu.htm">ALWNULL (Allow Null Value) keyword—physical files only</a></strong><br />
|
|
Use this field-level keyword to define this field to allow the null value.</li>
|
|
<li class="ulchildlink"><strong><a href="rzakbmsttdccsid.htm">CCSID (Coded Character Set Identifier) keyword for physical and logical files</a></strong><br />
|
|
Use this file- or field-level keyword on physical files and this field-level keyword on logical files to specify a coded character set identifier (CCSID) for character fields.</li>
|
|
<li class="ulchildlink"><strong><a href="rzakbmsttdcheck.htm">CHECK (Check) keyword for physical and logical files</a></strong><br />
|
|
Use this field-level keyword to specify validity checking in display files.</li>
|
|
<li class="ulchildlink"><strong><a href="rzakbmsttdchkms.htm">CHKMSGID (Check Message Identifier) keyword for physical and logical files</a></strong><br />
|
|
Use this field-level keyword to identify an error message that is associated with validity checking keywords.</li>
|
|
<li class="ulchildlink"><strong><a href="rzakbmsttdcmp.htm">CMP (Comparison) keyword for physical and logical files</a></strong><br />
|
|
This keyword is equivalent to the COMP keyword.</li>
|
|
<li class="ulchildlink"><strong><a href="rzakbmsttdcolhd.htm">COLHDG (Column Heading) keyword for physical and logical files</a></strong><br />
|
|
Use this field-level keyword to specify column headings used as a label for this field by text management, the query utility, the data file utility (DFU), and the screen design aid (SDA).</li>
|
|
<li class="ulchildlink"><strong><a href="rzakbmstlcomp.htm">COMP (Comparison) keyword for physical and logical files</a></strong><br />
|
|
Use this field-level keyword to specify validity checking for the field you are defining when it is referred to later during display file creation. For logical files, you can also specify this keyword at the select/omit-field level. COMP is equivalent to CMP.</li>
|
|
<li class="ulchildlink"><strong><a href="rzakbmstlconcat.htm">CONCAT (Concatenate) keyword—logical files only</a></strong><br />
|
|
Use this field-level keyword when you want to combine two or more fields from the physical file record format into one field in the logical file record format you are defining. The name of this concatenated field must appear in positions 19 through 28.</li>
|
|
<li class="ulchildlink"><strong><a href="rzakbmsttddatfm.htm">DATFMT (Date Format) keyword for physical and logical files</a></strong><br />
|
|
Use this field-level keyword to specify the format of a date field. This keyword is valid only for date fields (data type L) or for logical file zoned fields (data type S), packed fields (data type P), or character fields (data type A) whose corresponding physical file fields are date fields (data type L).</li>
|
|
<li class="ulchildlink"><strong><a href="rzakbmsttddatse.htm">DATSEP (Date Separator) keyword for physical and logical files</a></strong><br />
|
|
Use this field-level keyword to specify the separator character for a date field. This keyword is valid only for date fields (data type L).</li>
|
|
<li class="ulchildlink"><strong><a href="rzakbmsttddexce.htm">DESCEND (Descend) keyword for physical and logical files</a></strong><br />
|
|
Use this key field-level keyword to specify that the values of this character, hexadecimal, or numeric key field are retrieved in descending sequence.</li>
|
|
<li class="ulchildlink"><strong><a href="rzakbmstpdft.htm">DFT (Default) keyword—physical files only</a></strong><br />
|
|
Use this field-level keyword to specify a default value for a field.</li>
|
|
<li class="ulchildlink"><strong><a href="rzakbmsttddigit.htm">DIGIT (Digit) keyword for physical and logical files</a></strong><br />
|
|
Use this key field-level keyword to specify that only the digit portion (farthest right 4 bits) of each byte of the key field is used when constructing a value associated with this key field. The zone portion is zero-filled.</li>
|
|
<li class="ulchildlink"><strong><a href="rzakbmstdtdynsl.htm">DYNSLT (Dynamic Select) keyword—logical files only</a></strong><br />
|
|
Use this file-level keyword to indicate that the selection and omission tests specified in the file (using select/omit specifications) are done at processing time. This keyword specifies dynamic select/omit rather than access path select/omit.</li>
|
|
<li class="ulchildlink"><strong><a href="rzakbmsttdedtcd.htm">EDTCDE (Edit Code) and EDTWRD (Edit Word) keywords for physical and logical files</a></strong><br />
|
|
Use these field-level keywords to specify editing for the field you are defining when the field is referenced later during display or printer file creation. The EDTCDE and EDTWRD keywords do not affect the physical or logical file.</li>
|
|
<li class="ulchildlink"><strong><a href="rzakbmsttdfcfo.htm">FCFO (First-Changed First-Out) keyword for physical and logical files</a></strong><br />
|
|
Use this file-level keyword to specify that if records with duplicate key values are retrieved from the same physical or logical file member, the record with the key value that was changed first is the first record retrieved. This is a first-changed first-out (FCFO) order.</li>
|
|
<li class="ulchildlink"><strong><a href="rzakbmsttdfifo.htm">FIFO (First-In First-Out) keyword for physical and logical files</a></strong><br />
|
|
Use this file-level keyword to specify that if records with duplicate key values are retrieved from the same physical or logical file member, they are to be retrieved in a first-in first-out (FIFO) order.</li>
|
|
<li class="ulchildlink"><strong><a href="rzakbmsttdfltpc.htm">FLTPCN (Floating-Point Precision) keyword for physical and logical files</a></strong><br />
|
|
Use this field-level keyword to specify the precision of a floating-point field.</li>
|
|
<li class="ulchildlink"><strong><a href="rzakbmstlformat.htm">FORMAT (Format) keyword for physical and logical files</a></strong><br />
|
|
Use this record-level keyword to specify that this record format is to share the field specifications for a previously defined record format. The name of the record format you are defining must be the name of the previously defined record format.</li>
|
|
<li class="ulchildlink"><strong><a href="rzakbmsttdjdftv.htm">JDFTVAL (Join Default Values) keyword—join logical files only</a></strong><br />
|
|
Use this file-level keyword in a join logical file so the system provides default values for fields when a join to a secondary file does not produce any records. JDFTVAL is valid only for join logical files.</li>
|
|
<li class="ulchildlink"><strong><a href="rzakbmsttdjdups.htm">JDUPSEQ (Join Duplicate Sequence) keyword—join logical files only</a></strong><br />
|
|
Use this join-level keyword to specify the order in which records with duplicate join fields are presented when your program reads a join logical file.</li>
|
|
<li class="ulchildlink"><strong><a href="rzakbmstljfile.htm">JFILE (Joined Files) keyword—join logical files only</a></strong><br />
|
|
Use this record-level keyword to identify the physical files containing the data to be accessed through the join logical file you are defining.</li>
|
|
<li class="ulchildlink"><strong><a href="rzakbmsttdjfld.htm">JFLD (Joined Fields) keyword—join logical files only</a></strong><br />
|
|
Use this join-level keyword to identify the <em>from</em> and <em>to</em> fields
|
|
whose values are used to join physical files in a join logical file. These
|
|
fields are both referred to as join fields.</li>
|
|
<li class="ulchildlink"><strong><a href="rzakbmstlgjoin.htm">JOIN (Join) keyword—join logical files only</a></strong><br />
|
|
Use this join-level keyword to identify which pair of files are joined by the join specification in which you specify this keyword.</li>
|
|
<li class="ulchildlink"><strong><a href="rzakbmsttdjref.htm">JREF (Join Reference) keyword—join logical files only</a></strong><br />
|
|
Use this field-level keyword in join logical files for fields whose names are specified in more than one physical file. This keyword identifies which physical file contains the field.</li>
|
|
<li class="ulchildlink"><strong><a href="rzakbmsttdlifo.htm">LIFO (Last-In First-Out) keyword for physical and logical files</a></strong><br />
|
|
Use this file-level keyword to specify that records with duplicate key values from the same physical file member are retrieved in a last-in first-out (LIFO) order.</li>
|
|
<li class="ulchildlink"><strong><a href="rzakbmsttdnoalt.htm">NOALTSEQ (No Alternative Collating Sequence) keyword for physical and logical files</a></strong><br />
|
|
Use this key field-level keyword to specify that the ALTSEQ keyword specified at the file level does not apply to this key field. If you specify ABSVAL or SIGNED for a key field, NOALTSEQ is automatically in effect, whether the NOALTSEQ keyword is specified for that key field.</li>
|
|
<li class="ulchildlink"><strong><a href="rzakbmstlpfile.htm">PFILE (Physical File) keyword—logical files only</a></strong><br />
|
|
Use this record-level keyword to identify the physical file(s) containing the data to be accessed through the record format that you are defining.</li>
|
|
<li class="ulchildlink"><strong><a href="rzakbmsttdrange.htm">RANGE (Range) keyword for physical and logical files</a></strong><br />
|
|
Specify this keyword at the field level, the select- or omit-field level, or both.</li>
|
|
<li class="ulchildlink"><strong><a href="rzakbmstpref.htm">REF (Reference) keyword—physical files only</a></strong><br />
|
|
Use this file-level keyword to specify the name of the file from which field descriptions are retrieved.</li>
|
|
<li class="ulchildlink"><strong><a href="rzakbmsttdrefac.htm">REFACCPTH (Reference Access Path Definition) keyword—logical files only</a></strong><br />
|
|
Use this file-level keyword to specify that the access path information for this logical file is to be copied from another physical or logical file.</li>
|
|
<li class="ulchildlink"><strong><a href="rzakbmstpreffld.htm">REFFLD (Referenced Field) keyword—physical files only</a></strong><br />
|
|
Use this field-level keyword to refer to a field under one of these three conditions.</li>
|
|
<li class="ulchildlink"><strong><a href="rzakbmsttdrefsh.htm">REFSHIFT (Reference Shift) keyword for physical and logical files</a></strong><br />
|
|
Use this field-level keyword to specify a keyboard shift for a field when the field is referred to in a display file or data file utility (DFU) operation.</li>
|
|
<li class="ulchildlink"><strong><a href="rzakbmsttdrenam.htm">RENAME (Rename) keyword—logical files only</a></strong><br />
|
|
Use this field-level keyword when you want a field name in the logical record format that you are defining to be different from its corresponding physical file field name.</li>
|
|
<li class="ulchildlink"><strong><a href="rzakbmstsign.htm">SIGNED (Signed) keyword for physical and logical files</a></strong><br />
|
|
Use this key field-level keyword to specify that when sequencing the values associated with this numeric key field, the operating system is to consider the signs of the values (negative versus positive values).</li>
|
|
<li class="ulchildlink"><strong><a href="rzakbmsttdsst.htm">SST (Substring) keyword—logical files only</a></strong><br />
|
|
Use this field-level keyword to specify a character string that is a subset of an existing character, hexadecimal, zoned field, or graphic.</li>
|
|
<li class="ulchildlink"><strong><a href="rzakbmsttdtext.htm">TEXT (Text) keyword for physical and logical files</a></strong><br />
|
|
Use this record- or field-level keyword to supply a text description (or comment) for the record format or field that is used for program documentation.</li>
|
|
<li class="ulchildlink"><strong><a href="rzakbmsttdtimfm.htm">TIMFMT (Time Format) keyword for physical and logical files</a></strong><br />
|
|
Use this field-level keyword to specify the format of a time field. This keyword is valid for either time fields (data type T) or zoned fields (data type S) whose corresponding physical file fields are time fields (data type T).</li>
|
|
<li class="ulchildlink"><strong><a href="rzakbmsttdtimse.htm">TIMSEP (Time Separator) keyword for physical and logical files</a></strong><br />
|
|
Use this field-level keyword to specify the separator character used for a time field. This keyword is valid only for time fields (data type T).</li>
|
|
<li class="ulchildlink"><strong><a href="rzakbmsttdtrntb.htm">TRNTBL (Translation Table) keyword—logical files only</a></strong><br />
|
|
Use this field-level keyword to specify the name of a translation table to be used when passing this field between the physical file on the PFILE or JFILE keyword and your program.</li>
|
|
<li class="ulchildlink"><strong><a href="rzakbmsttduniqu.htm">UNIQUE (Unique) keyword for physical and logical files</a></strong><br />
|
|
Use this file-level keyword to specify that records with duplicate key values are not allowed within a member of this physical or logical file.</li>
|
|
<li class="ulchildlink"><strong><a href="rzakbmsttdunsig.htm">UNSIGNED (Unsigned) keyword for physical and logical files</a></strong><br />
|
|
Use this key field-level keyword to specify that numeric fields are sequenced as a string of unsigned binary data. Character, date, time, timestamp, and hexadecimal fields default to unsigned values.</li>
|
|
<li class="ulchildlink"><strong><a href="rzakbmsttdvalue.htm">VALUES (Values) keyword for physical and logical files</a></strong><br />
|
|
Specify this keyword at the field level, the select/omit-field level, or both.</li>
|
|
<li class="ulchildlink"><strong><a href="rzakbmsttdvarle.htm">VARLEN (Variable-Length Field) keyword for physical and logical files</a></strong><br />
|
|
Use this field-level keyword to define this field as a variable-length field.</li>
|
|
<li class="ulchildlink"><strong><a href="rzakbmsttdzone.htm">ZONE (Zone) keyword for physical and logical files</a></strong><br />
|
|
Use this key field-level keyword to specify that only the zone portion (farthest left 4 bits) of each byte of the key field is used when constructing a value associated with this key field. The digit portion is filled with zeros.</li>
|
|
</ul>
|
|
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="kickoff.htm" title="You can use data description specifications (DDS) to define physical and logical database files. This topic provides the information you need to code the positional and keyword entries that define these files.">DDS for physical and logical files</a></div>
|
|
</div>
|
|
<div class="relref"><strong>Related reference</strong><br />
|
|
<div><a href="dbkwd.htm" title="Do not specify DDS keywords intended for use with numeric data for fields containing DBCS data. The system treats DBCS data the same as character data, and, therefore, cannot perform arithmetic operations on it.">Keyword considerations for database files that use DBCS</a></div>
|
|
</div>
|
|
<div class="relinfo"><strong>Related information</strong><br />
|
|
<div><a href="../dds/rbafpmstsyntax.htm">Rules for DDS keywords and parameter values</a></div>
|
|
</div>
|
|
</div>
|
|
</body>
|
|
</html> |