73 lines
4.8 KiB
HTML
73 lines
4.8 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="Field name" />
|
|
<meta name="abstract" content="When position 17 is left blank, the name specified in positions 19 through 28 is a field name." />
|
|
<meta name="description" content="When position 17 is left blank, the name specified in positions 19 through 28 is a field name." />
|
|
<meta name="DC.subject" content="field name, physical files, field name, logical files" />
|
|
<meta name="keywords" content="field name, physical files, field name, logical files" />
|
|
<meta name="DC.Relation" scheme="URI" content="lfname.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakbmstlconcat.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="fieldname" />
|
|
<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>Field name</title>
|
|
</head>
|
|
<body id="fieldname"><a name="fieldname"><!-- --></a>
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|
<h1 class="topictitle1">Field name</h1>
|
|
<div><p>When position 17 is left blank, the name specified in positions
|
|
19 through 28 is a field name.</p>
|
|
<p>You cannot specify field names if you specify the FORMAT keyword.</p>
|
|
<p>Physical files require that each field be named. These names must be unique
|
|
within the record format. The field names appear in the physical buffer in
|
|
the same order as they are specified in the DDS.</p>
|
|
<p>If you are describing a simple or multiple format logical file, you can
|
|
use the record format as it exists in the physical file on which this logical
|
|
file is based, and you do not need to specify field names.</p>
|
|
<p>If you do not use the record format as it exists in the physical file,
|
|
you must name each field specified in a logical file. In a simple or multiple
|
|
format logical file, each field name must be unique within the record format
|
|
and must correspond to a field in the physical file record format. The field
|
|
name order is the order in which the fields appear to programs using the logical
|
|
file.</p>
|
|
<div class="p">The name you give to a field in a logical file record format is typically
|
|
the same as the corresponding field name in the physical file record format.
|
|
If different, the two names must be equated by using the RENAME keyword. A
|
|
field in a logical file record format can also represent the concatenation
|
|
of two or more fields from the physical file. The SST keyword can also be
|
|
used to describe a substring of a field from the physical file in the logical
|
|
file format. <div class="note"><span class="notetitle">Note:</span> The sequence in which the field names are specified in
|
|
the logical file is important. If the same physical field is specified more
|
|
than once in a record format in the logical file (by using either RENAME or
|
|
CONCAT), the sequence in which the fields are specified in the logical file
|
|
is the sequence that the data is moved to the physical file. Thus, the value
|
|
of the field specified in the logical file the last time is the
|
|
value in the physical record.</div>
|
|
</div>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="lfname.htm" title="Use these positions to specify record or field names.">Name for physical and logical files (positions 19 through 28)</a></div>
|
|
</div>
|
|
<div class="relref"><strong>Related reference</strong><br />
|
|
<div><a href="rzakbmstlconcat.htm" title="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.">CONCAT (Concatenate) keyword—logical files only</a></div>
|
|
</div>
|
|
</div>
|
|
</body>
|
|
</html> |