115 lines
6.7 KiB
HTML
115 lines
6.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="reference" />
|
||
|
|
<meta name="DC.Title" content="Usage for physical and logical files (position 38)" />
|
||
|
|
<meta name="abstract" content="Use this field to specify that a named field is to be an input-only, both (both input and output are allowed), or neither field." />
|
||
|
|
<meta name="description" content="Use this field to specify that a named field is to be an input-only, both (both input and output are allowed), or neither field." />
|
||
|
|
<meta name="DC.subject" content="usage, logical files, physical files" />
|
||
|
|
<meta name="keywords" content="usage, logical files, physical files" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakbmstlfpos.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakbmstpdft.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakbmsttdjfld.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="lfusg" />
|
||
|
|
<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>Usage for physical and logical files (position 38)</title>
|
||
|
|
</head>
|
||
|
|
<body id="lfusg"><a name="lfusg"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Usage for physical and logical files (position 38)</h1>
|
||
|
|
<div><p>Use this field to specify that a named field is to be an input-only,
|
||
|
|
both (both input and output are allowed), or neither field.</p>
|
||
|
|
<div class="section"><div class="p">For physical files, you can specify the following entries: <dl><dt><strong>Entry</strong></dt>
|
||
|
|
<dd><strong>Meaning</strong></dd>
|
||
|
|
<dt class="dlterm">Blank</dt>
|
||
|
|
<dd>Defaults to B (both input and output allowed)</dd>
|
||
|
|
<dt class="dlterm">B</dt>
|
||
|
|
<dd>Both input and output allowed</dd>
|
||
|
|
</dl>
|
||
|
|
</div>
|
||
|
|
<p>Because the default is the same as the only value, you
|
||
|
|
do not need to make an entry in this field.</p>
|
||
|
|
<p>Entries in position 38 are
|
||
|
|
not referred to by the REF or REFFLD keywords. Therefore, a B in position
|
||
|
|
38 for a field in a physical file has no effect when that field is referred
|
||
|
|
to in a display file.</p>
|
||
|
|
<div class="p">The valid entries for logical files are described
|
||
|
|
as follows: <dl><dt class="dlterm">Blank (Default)</dt>
|
||
|
|
<dd>If position 38 is blank, the following situation occurs:
|
||
|
|
<ul><li>For simple and multiple format logical files (PFILE specified at the record
|
||
|
|
level), the field is a both (B) field.</li>
|
||
|
|
<li>For join logical files (JFILE specified at the record level), the field
|
||
|
|
is an input-only (I) field.</li>
|
||
|
|
</ul>
|
||
|
|
</dd>
|
||
|
|
<dt class="dlterm">B (Both)</dt>
|
||
|
|
<dd>If position 38 is B, the field is a <em>both</em> field and can be used
|
||
|
|
for both input and output operations. That is, your program can read data
|
||
|
|
from the field and write data to the field. Both fields are not valid for
|
||
|
|
join logical files, because join logical files are read-only files.</dd>
|
||
|
|
<dt class="dlterm">I (Input-Only)</dt>
|
||
|
|
<dd>If position 38 is I, the field is an <em>input-only</em> field and can be
|
||
|
|
used for input operations only. That is, your program can read data from the
|
||
|
|
field, but cannot change the field. Typical cases of input-only fields are
|
||
|
|
key fields (to reduce maintenance of access paths), sensitive fields that
|
||
|
|
a user can see but not change (such as, in employee records, salary), and
|
||
|
|
fields for which the SST or TRNTBL keyword is specified. <p>If your program
|
||
|
|
performs a change to a record format in which you have specified input-only
|
||
|
|
fields, the input-only fields are not updated and no message is sent. If your
|
||
|
|
program performs an output operation to a record format in which you have
|
||
|
|
specified input-only fields, the input-only fields take default values (see
|
||
|
|
the DFT (Default) keyword-physical files only topic).</p>
|
||
|
|
<p>Input-only fields
|
||
|
|
are not valid in physical files.</p>
|
||
|
|
</dd>
|
||
|
|
<dt class="dlterm">N (Neither)</dt>
|
||
|
|
<dd>If position 38 is N, the field is a <em>neither</em> field (neither input
|
||
|
|
nor output) and is valid only for join logical files. A neither field can
|
||
|
|
be used as a join field in a join logical file, but your program cannot read
|
||
|
|
a neither field. <p>Use neither fields when the attributes of join fields
|
||
|
|
in the physical files do not match. In this case, one or both join fields
|
||
|
|
must be redefined. However, you might not want to include the redefined fields
|
||
|
|
in the record format (that is, you might not want the application program
|
||
|
|
to see the redefined fields). Therefore, code the redefined join fields as
|
||
|
|
N and they do not appear in the record format.</p>
|
||
|
|
<p>A field with N in position
|
||
|
|
38 does not appear in the buffer used by your program. However, the field
|
||
|
|
description is displayed with the Display File Field Description (DSPFFD)
|
||
|
|
command.</p>
|
||
|
|
<p><em>Neither</em> fields cannot be used as select/omit
|
||
|
|
or key fields.</p>
|
||
|
|
</dd>
|
||
|
|
</dl>
|
||
|
|
</div>
|
||
|
|
<p>Entries in position 38 are not referred to using
|
||
|
|
the REF or REFFLD keyword. Therefore, a B or an I in position 38 for a field
|
||
|
|
in a logical file has no effect when that field is referred to in a display
|
||
|
|
file.</p>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzakbmstlfpos.htm" title="The first 44 positions of the DDS form are called positional entries.">Positional entries for physical and logical files (positions 1 through 44)</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relref"><strong>Related reference</strong><br />
|
||
|
|
<div><a href="rzakbmstpdft.htm" title="Use this field-level keyword to specify a default value for a field.">DFT (Default) keyword—physical files only</a></div>
|
||
|
|
<div><a href="rzakbmsttdjfld.htm" title="Use this join-level keyword to identify the from and to fields whose values are used to join physical files in a join logical file. These fields are both referred to as join fields.">JFLD (Joined Fields) keyword—join logical files only</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|