108 lines
6.7 KiB
HTML
108 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="JFILE (Joined Files) keyword—join logical files only" />
|
|||
|
|
<meta name="abstract" content="Use this record-level keyword to identify the physical files containing the data to be accessed through the join logical file you are defining." />
|
|||
|
|
<meta name="description" content="Use this record-level keyword to identify the physical files containing the data to be accessed through the join logical file you are defining." />
|
|||
|
|
<meta name="DC.subject" content="JFILE (Joined Files) keyword, Joined Files (JFILE) keyword" />
|
|||
|
|
<meta name="keywords" content="JFILE (Joined Files) keyword, Joined Files (JFILE) keyword" />
|
|||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakbmstlfkeyw.htm" />
|
|||
|
|
<meta name="DC.Relation" scheme="URI" content="../ddm/rbae5kickoff.htm" />
|
|||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakbmstlgjoin.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="ljfile" />
|
|||
|
|
<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, JFILE</title>
|
|||
|
|
</head>
|
|||
|
|
<body id="ljfile"><a name="ljfile"><!-- --></a>
|
|||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|||
|
|
<h1 class="topictitle1">JFILE (Joined Files) keyword—join logical files only</h1>
|
|||
|
|
<div><p>Use this record-level keyword to identify the physical files containing
|
|||
|
|
the data to be accessed through the join logical file you are defining.</p>
|
|||
|
|
<div class="section"><div class="p">The format of the keyword is: <pre>JFILE([library-name/]physical-file-name [..256])</pre>
|
|||
|
|
</div>
|
|||
|
|
<p>This
|
|||
|
|
keyword is similar to the PFILE keyword except that it identifies this file
|
|||
|
|
as a join logical file. The JFILE keyword is not allowed with the PFILE keyword.</p>
|
|||
|
|
<p>The
|
|||
|
|
JFILE keyword is required at the record level in a join logical file. The
|
|||
|
|
JFILE keyword requires a minimum of two physical file names. You can specify
|
|||
|
|
the same file name more than once.</p>
|
|||
|
|
<p>The first
|
|||
|
|
file is called the primary file, which is the file from which the join begins.
|
|||
|
|
All other files are called secondary files. Up to 255 secondary files can
|
|||
|
|
be specified (256 total files on the JFILE keyword).</p>
|
|||
|
|
<p>Distributed data
|
|||
|
|
management (DDM) files are allowed on the JFILE keyword only when the logical
|
|||
|
|
file is being created on a remote system. See the Distributed data management
|
|||
|
|
topic for more information.</p>
|
|||
|
|
<div class="p">The following considerations apply to the
|
|||
|
|
order in which you specify physical files on the JFILE keyword: <ul><li>If the physical files have a different number of records, specify physical
|
|||
|
|
files with fewer records toward the left on the JFILE keyword. The primary
|
|||
|
|
file should have as many or fewer records than the secondary files. This can
|
|||
|
|
improve performance when reading files.</li>
|
|||
|
|
<li>Primary and secondary files specified in join specifications must be in
|
|||
|
|
a specific order. This order depends on the order in which the files are specified
|
|||
|
|
on the JFILE keyword. See example 3 in the JOIN (Join) keyword description.</li>
|
|||
|
|
<li>The JOIN and JREF keywords can use relative file numbers
|
|||
|
|
to identify files specified by the JFILE keyword. The first file specified
|
|||
|
|
on the JFILE keyword has relative file number 1, the second file has relative
|
|||
|
|
file number 2, and so on up to 256. If you use relative file numbers
|
|||
|
|
instead of file names on the JOIN and JREF keywords, the order of files on
|
|||
|
|
the JFILE keyword can affect the way the JOIN and JREF keywords are specified.</li>
|
|||
|
|
</ul>
|
|||
|
|
<div class="note"><span class="notetitle">Note:</span> If the names in the physical file are not unique, you must specify
|
|||
|
|
relative file numbers.</div>
|
|||
|
|
</div>
|
|||
|
|
</div>
|
|||
|
|
<div class="example"><h4 class="sectiontitle">Examples</h4><p>The following examples show how to specify
|
|||
|
|
the JFILE keyword.</p>
|
|||
|
|
<pre>|...+....1....+....2....+....3....+....4....+....5....+....6....+....7....+....8
|
|||
|
|
00010A R JREC JFILE(PF1 PF2)
|
|||
|
|
00020A J JOIN(PF1 PF2)
|
|||
|
|
00030A JFLD(NAME1 NAME2)
|
|||
|
|
A</pre>
|
|||
|
|
<p>In the join logical file, PF1 is the primary file and
|
|||
|
|
PF2 is the secondary file.</p>
|
|||
|
|
</div>
|
|||
|
|
<div class="example"> <pre>|...+....1....+....2....+....3....+....4....+....5....+....6....+....7....+....8
|
|||
|
|
00010A R JREC JFILE(MYLIBA/PHYSICAL1 +
|
|||
|
|
00020A MYLIBB/PHYSICAL2 MYLIBC/PHYSICAL3)
|
|||
|
|
00030A J JOIN(1 2)
|
|||
|
|
00040A JFLD(FIELD1 FIELD2)
|
|||
|
|
00050A J JOIN(1 3)
|
|||
|
|
00060A JFLD(FIELD1 FIELD2)
|
|||
|
|
A</pre>
|
|||
|
|
<p>In the join logical file, file PHYSICAL1 in library MYLIBA
|
|||
|
|
is the primary file. File PHYSICAL2 in library MYLIBB and file PHYSICAL3 in
|
|||
|
|
library MYLIBC are secondary files.</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 class="relref"><strong>Related reference</strong><br />
|
|||
|
|
<div><a href="rzakbmstlgjoin.htm" title="Use this join-level keyword to identify which pair of files are joined by the join specification in which you specify this keyword.">JOIN (Join) keyword—join logical files only</a></div>
|
|||
|
|
</div>
|
|||
|
|
<div class="relinfo"><strong>Related information</strong><br />
|
|||
|
|
<div><a href="../ddm/rbae5kickoff.htm">Distributed data management</a></div>
|
|||
|
|
</div>
|
|||
|
|
</div>
|
|||
|
|
</body>
|
|||
|
|
</html>
|