86 lines
5.6 KiB
HTML
86 lines
5.6 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="task" />
|
||
|
|
<meta name="DC.Title" content="Set up a join logical file" />
|
||
|
|
<meta name="abstract" content="This topic shows how to set up a join logical file." />
|
||
|
|
<meta name="description" content="This topic shows how to set up a join logical file." />
|
||
|
|
<meta name="DC.subject" content="setting up, join logical file, file, logical, logical file, join" />
|
||
|
|
<meta name="keywords" content="setting up, join logical file, file, logical, logical file, join" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbafojnlof.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbafonflds.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="rbafosetlf" />
|
||
|
|
<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>Set up a join logical file</title>
|
||
|
|
</head>
|
||
|
|
<body id="rbafosetlf"><a name="rbafosetlf"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Set up a join logical file</h1>
|
||
|
|
<div><p>This topic shows how to set up a join logical file.</p>
|
||
|
|
<div class="section"> <p>To set up a join logical file, follow these steps:</p>
|
||
|
|
</div>
|
||
|
|
<ol><li class="stepexpand"><span>Find the names of all the physical file fields you want in the
|
||
|
|
logical file record format. (You can display the fields contained in files
|
||
|
|
using the Display File Field Description (DSPFFD) command.)</span></li>
|
||
|
|
<li class="stepexpand"><span>Describe the fields in the record format.</span> Write the
|
||
|
|
field names in a vertical list. This is the start of the record format for
|
||
|
|
the join logical file. <div class="note"><span class="notetitle">Note:</span> You can specify the field names in any order.
|
||
|
|
If the same field names appear in different physical files, specify the name
|
||
|
|
of the physical file on the JREF keyword for those fields. You can rename
|
||
|
|
fields using the RENAME keyword, and concatenate fields from the same physical
|
||
|
|
file using the CONCAT keyword. A subset of an existing character, hexadecimal,
|
||
|
|
or zoned decimal field can be defined using the SST keyword. The substring
|
||
|
|
of a character or zoned decimal field is a character field, and the substring
|
||
|
|
of a hexadecimal field is also a hexadecimal field. You can redefine fields:
|
||
|
|
changing their data type, length, or decimal positions.</div>
|
||
|
|
</li>
|
||
|
|
<li class="stepexpand"><span>Specify the names of the physical files as parameter values on
|
||
|
|
the JFILE keyword. </span> The first name you specify is the primary file.
|
||
|
|
The others are all secondary files. For best performance, specify the secondary
|
||
|
|
files with the least records first after the primary file.</li>
|
||
|
|
<li class="stepexpand"><span>For each secondary file, code a join specification. </span> On
|
||
|
|
each join specification, identify which pair of files are joined (using the
|
||
|
|
JOIN keyword; optional if only one secondary file), and identify which fields
|
||
|
|
are used to join the pair (using the JFLD keyword; at least one required in
|
||
|
|
each join specification).</li>
|
||
|
|
<li class="stepexpand"><strong>Optional: </strong><span>Specify the following items:</span> <ol type="a"><li>The JDFTVAL keyword. Do this if you want to return a record for each record
|
||
|
|
in the primary file even if no matching record exists in a secondary file.</li>
|
||
|
|
<li>The JDUPSEQ keyword. Do this for fields that might have duplicate values
|
||
|
|
in the secondary files. JDUPSEQ specifies on which field (other than one of
|
||
|
|
the join fields) to sort these duplicates, and the sequence that should be
|
||
|
|
used.</li>
|
||
|
|
<li>Key fields. Key fields cannot come from a secondary file. If you omit
|
||
|
|
key fields, records are returned in arrival sequence as they appear in the
|
||
|
|
primary file.</li>
|
||
|
|
<li>Select/omit fields. In some situations, you must also specify the dynamic
|
||
|
|
selection (DYNSLT) keyword at the file level.</li>
|
||
|
|
<li>Neither fields.</li>
|
||
|
|
</ol>
|
||
|
|
</li>
|
||
|
|
</ol>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbafojnlof.htm" title="These topics provide examples to illustrate how to set up a join logical file. Performance, integrity, and a summary of rules for join logical files are also included.">Set up a join logical file</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relref"><strong>Related reference</strong><br />
|
||
|
|
<div><a href="rbafonflds.htm" title="Neither fields, which (N specified in position 38) can be used in join logical file for neither input nor output, are not included in the record format. This example shows how to describe such fields that never appear in the record format.">Describe fields that never appear in the record format (example 5)</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|