97 lines
5.7 KiB
HTML
97 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="JREF (Join Reference) keyword—join logical files only" />
|
||
|
|
<meta name="abstract" content="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." />
|
||
|
|
<meta name="description" content="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." />
|
||
|
|
<meta name="DC.subject" content="JREF (Join Reference) keyword, Join Reference (JREF) keyword" />
|
||
|
|
<meta name="keywords" content="JREF (Join Reference) keyword, Join Reference (JREF) keyword" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakbmstlfkeyw.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="tdjref" />
|
||
|
|
<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>Physical and Logical Files, JREF</title>
|
||
|
|
</head>
|
||
|
|
<body id="tdjref"><a name="tdjref"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">JREF (Join Reference) keyword—join logical files only </h1>
|
||
|
|
<div><p>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.</p>
|
||
|
|
<div class="section"><div class="p">The format of the keyword is: <pre>JREF(file-name | relative-file-number)</pre>
|
||
|
|
</div>
|
||
|
|
<p>You
|
||
|
|
can specify either the physical file name or its relative file number. If
|
||
|
|
a physical file is named twice on the JFILE keyword, then you must specify
|
||
|
|
the relative file number. The relative file number corresponds to the physical
|
||
|
|
file name specified on the JFILE keyword. For example, specifying JREF(1)
|
||
|
|
associates a field with the first physical file specified on the JFILE keyword.
|
||
|
|
Specifying JREF(2) associates a field with the second physical file specified
|
||
|
|
on the JFILE keyword. See example 2 in this topic.</p>
|
||
|
|
<p>This
|
||
|
|
keyword is valid only in a join logical file.</p>
|
||
|
|
<p>Join logical files are
|
||
|
|
based on two or more physical files (up to 256). Field names specified in
|
||
|
|
the record format in a join logical file must uniquely identify only one field
|
||
|
|
from the physical files on which the join logical file is based. For example,
|
||
|
|
if the join logical file is based on two physical files, and each physical
|
||
|
|
file has the field named NAME, you must specify the JREF keyword to identify
|
||
|
|
which physical file the field comes from.</p>
|
||
|
|
<p>When a field name is unique
|
||
|
|
among the physical files specified on the JFILE keyword, this keyword is optional.
|
||
|
|
For example, if the join logical file is associated with two physical files,
|
||
|
|
and only one of the physical files has a field named NAME1, you do not need
|
||
|
|
to specify the JREF keyword.</p>
|
||
|
|
<p>If the join logical file is associated
|
||
|
|
with only one physical file (the JFILE keyword names the same file twice),
|
||
|
|
you must specify the JREF keyword on every field.</p>
|
||
|
|
</div>
|
||
|
|
<div class="example"><h4 class="sectiontitle">Example 1</h4><p>The following examples show how to specify
|
||
|
|
the JREF keyword.</p>
|
||
|
|
<pre>|...+....1....+....2....+....3....+....4....+....5....+....6....+....7....+....8
|
||
|
|
00010A R JOINREC JFILE(PFA PFB PFC)
|
||
|
|
00020A :
|
||
|
|
00030A :
|
||
|
|
00040A :
|
||
|
|
00050A NAME JREF(PFB)
|
||
|
|
A</pre>
|
||
|
|
<p>In this example, the JREF keyword is specified with the
|
||
|
|
file name, and NAME occurs in both PFA and PFB. Specifying JREF (PFB) associates
|
||
|
|
this field with PFB.</p>
|
||
|
|
</div>
|
||
|
|
<div class="example"><h4 class="sectiontitle">Example 2</h4><p>The following example shows how to use
|
||
|
|
the file reference numbers to specify JREF.</p>
|
||
|
|
<pre>|...+....1....+....2....+....3....+....4....+....5....+....6....+....7....+....8
|
||
|
|
00010A R JOINREC JFILE(PFA PFB PFC)
|
||
|
|
00020A :
|
||
|
|
00030A :
|
||
|
|
00040A :
|
||
|
|
00050A NAME JREF(2)
|
||
|
|
A</pre>
|
||
|
|
<p>Example 2 is equivalent to example 1. In example 2, NAME
|
||
|
|
occurs in both PFA and PFB. Specifying JREF(2) associates this field with
|
||
|
|
PFB (the second of the physical files specified on the JFILE keyword).</p>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzakbmstlfkeyw.htm" title="This topic lists valid keyword entries for describing physical and logical files. They are typed in positions 45 through 80 (functions).">Keyword entries for physical and logical files (positions 45 through 80)</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|