89 lines
5.7 KiB
HTML
89 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="reference" />
|
||
|
|
<meta name="DC.Title" content="Field names" />
|
||
|
|
<meta name="abstract" content="Listed here are the requirements for specifying field names on the Open Query File (OPNQRYF) command parameters." />
|
||
|
|
<meta name="description" content="Listed here are the requirements for specifying field names on the Open Query File (OPNQRYF) command parameters." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbafoopnqf.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="rbafofn" />
|
||
|
|
<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 names</title>
|
||
|
|
</head>
|
||
|
|
<body id="rbafofn"><a name="rbafofn"><!-- --></a>
|
||
|
|
<img src="./delta.gif" alt="Start of change" /><!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Field names</h1>
|
||
|
|
<div><p>Listed here are the requirements for specifying field names on
|
||
|
|
the Open Query File (OPNQRYF) command parameters.</p>
|
||
|
|
<div class="section"><p>The field name used as the first part of an element in the list
|
||
|
|
specified on the MAPFLD parameter must be a simple name, and the field names
|
||
|
|
in the record format identified on the FORMAT parameter are always treated
|
||
|
|
as simple names. Any other field name specified on an OPNQRYF command parameter
|
||
|
|
(QRYSLT, KEYFLD, JFLD, GRPFLD, GRPSLT, or the field-definition expression
|
||
|
|
part of the MAPFLD parameter) is a qualified field name, specified as follows:</p>
|
||
|
|
<dl><dt class="dlterm">field-name</dt>
|
||
|
|
<dd>Specify a simple field name that identifies a field that is defined on
|
||
|
|
the MAPFLD parameter, or with a field name that is unique among all field
|
||
|
|
names from all record formats included in the list specified on the FILE parameter.
|
||
|
|
This form is not allowed if there is no MAPFLD parameter definition for the
|
||
|
|
specified field name and the FILE parameter includes more than one record
|
||
|
|
format that contains a field with the specified name, even if the same file
|
||
|
|
and record format is specified more than once in the list on the FILE parameter. <p>For
|
||
|
|
example, AMOUNT is valid if the field named AMOUNT is defined on the MAPFLD
|
||
|
|
parameter. It is also valid if AMOUNT is not defined on the MAPFLD parameter,
|
||
|
|
as long as there is only one field named AMOUNT in any record format specified
|
||
|
|
on the FILE parameter.</p>
|
||
|
|
</dd>
|
||
|
|
<dt class="dlterm">file-name/field-name</dt>
|
||
|
|
<dd>Specify a field name that is qualified with the simple name of the file
|
||
|
|
specified on the FILE parameter whose record format contains the field, but
|
||
|
|
only if the simple file name is unique among all file names specified on the
|
||
|
|
FILE parameter. This form is not allowed if the same simple file name is specified
|
||
|
|
more than once in the list specified for the FILE parameter, even if different
|
||
|
|
library, member, or record format names are used. <p>For example, WHS01/PARTNBR
|
||
|
|
is valid if there is a field named PARTNBR in the record format for file WHS01,
|
||
|
|
and file name WHS01 is only specified once on the FILE parameter.</p>
|
||
|
|
</dd>
|
||
|
|
<dt class="dlterm">file-nbr/field-name</dt>
|
||
|
|
<dd>Specify a simple field name that is qualified with the number of the element
|
||
|
|
in the FILE parameter list for the record format that contains the field.
|
||
|
|
The file-nbr qualifier must be specified without leading zeros. This form
|
||
|
|
is only required if the same simple file name is specified more than once
|
||
|
|
in the list specified on the FILE parameter.<p>For example, 2/BALDUE is valid
|
||
|
|
if the second file record format in the list specified on the FILE parameter
|
||
|
|
contains a field named BALDUE.</p>
|
||
|
|
</dd>
|
||
|
|
<dt class="dlterm">*MAPFLD/field-name</dt>
|
||
|
|
<dd>Specify a simple field name that is qualified with the special value *MAPFLD
|
||
|
|
if the field is defined on the MAPFLD parameter. When the field is defined,
|
||
|
|
this form has the same meaning as specifying the simple field name with no
|
||
|
|
qualifier. If the field is not defined on the MAPFLD parameter, *MAPFLD cannot
|
||
|
|
be specified. <p>For example, *MAPFLD/AVGBAL is valid if the AVGBAL field
|
||
|
|
is specified as the first part of one of the mapped field list elements specified
|
||
|
|
on the MAPFLD parameter.</p>
|
||
|
|
</dd>
|
||
|
|
</dl>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbafoopnqf.htm" title="The Open Query File (OPNQRYF) command is a control language (CL) command that allows you to perform many data processing functions on database files. These topics discuss how to create a query using the OPNQRYF command, how to specify parameters for its major functions, and how to use it with your high-level language program.">Use Open Query File (OPNQRYF) command</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<img src="./deltaend.gif" alt="End of change" /></body>
|
||
|
|
</html>
|