ibm-information-center/dist/eclipse/plugins/i5OS.ic.ddm_5.4.0.1/rbae5ovr3836.htm

119 lines
7.4 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="Override considerations to System/36 for DDM" />
<meta name="abstract" content="When a file override is issued on the iSeries server to get records in a logical file on a System/36, the results might be different than expected because of the difference in how each system deals with keyed files." />
<meta name="description" content="When a file override is issued on the iSeries server to get records in a logical file on a System/36, the results might be different than expected because of the difference in how each system deals with keyed files." />
<meta name="DC.subject" content="target DDM (TDDM), System/36, override considerations, TDDM (target DDM), recursion level, override considerations, logical file" />
<meta name="keywords" content="target DDM (TDDM), System/36, override considerations, TDDM (target DDM), recursion level, override considerations, logical file" />
<meta name="DC.Relation" scheme="URI" content="rbae5source36.htm" />
<meta name="copyright" content="(C) Copyright IBM Corporation 1999, 2006" />
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 1999, 2006" />
<meta name="DC.Format" content="XHTML" />
<meta name="DC.Identifier" content="rbae5ovr3836" />
<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>Override considerations to System/36 for
DDM</title>
</head>
<body id="rbae5ovr3836"><a name="rbae5ovr3836"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">Override considerations to <span class="keyword">System/36</span> for
DDM</h1>
<div><p>When a file override is issued on the <span class="keyword">iSeries™ server</span> to
get records in a logical file on a <span class="keyword">System/36™</span>,
the results might be different than expected because of the difference in
how each system deals with keyed files.</p>
<div class="section"><p>An <span class="keyword">iSeries server</span> uses
access paths and logical files, which produce a single view of a file. A <span class="keyword">System/36</span> logical file can be considered
a list of keys and relative record numbers.</p>
</div>
<div class="section"><p>When an <span class="keyword">iSeries server</span> accesses
a <span class="keyword">System/36</span> logical file:</p>
<ul><li>If you specify a relative record number, you receive the record from the
underlying <span class="keyword">System/36</span> base file
that corresponds to that record number. Then if you request to read the next
record, you receive the next sequential record from the base file.</li>
<li>If you specify a key, you receive the record that corresponds to the first
occurrence of that key in the index file. If you request to read the next
record, you receive the record that matches the next entry in the index file.</li>
</ul>
</div>
<div class="section"><p>The following example shows the various results for records being
retrieved from a <span class="keyword">System/36</span> logical
file by an <span class="keyword">iSeries</span> program.
The example assumes that:</p>
<ul><li>File S36FILEA is the base file and S36FILEB is the logical file that is
built over the base file.</li>
<li>Both files have DDM files named S36FILEA and S36FILEB that point to corresponding
remote files on the target <span class="keyword">System/36</span>.</li>
<li>The key field is numeric and it always contains the record number.</li>
<li>The records in the base file (S36FILEA) are in ascending sequence by key,
and the records in the logical file (S36FILEB) are in descending sequence
with the same key.</li>
<li>To create the results shown in the following table, the POSITION parameter
value is shown to vary, and no NBRRCDS parameter is specified on either command
(which means the total records read is dependent only on the POSITION parameter
value).<pre>OVRDBF FILE(S36FILEA) TOFILE(S36FILEB)
POSITION(*RRN ... or *KEY ...)
CPYF FROMFILE(S36FILEA) TOFILE(ISERIESFILEB)
CRTFILE(*YES) FMTOPT(*NOCHK)</pre>
</li>
</ul>
</div>
<div class="section"><p>Depending on the values specified on the <span class="cmdname">Override with
Database File (OVRDBF)</span> command for the POSITION parameter, the following
are the resulting records that are copied into the file ISERIESFILEB when
it is created on the source <span class="keyword">iSeries server</span>:</p>
</div>
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" width="100%" frame="border" border="1" rules="all"><thead align="left"><tr><th align="left" valign="bottom" width="50%" id="d0e142">POSITION parameter (See note)</th>
<th align="left" valign="bottom" width="50%" id="d0e144">Resulting records retrieved</th>
</tr>
</thead>
<tbody><tr><td align="left" valign="top" width="50%" headers="d0e142 ">*RRN 1</td>
<td align="left" valign="top" width="50%" headers="d0e144 ">299 records, 1 through 299</td>
</tr>
<tr><td align="left" valign="top" width="50%" headers="d0e142 ">*KEY 1</td>
<td align="left" valign="top" width="50%" headers="d0e144 ">1 record, first record only</td>
</tr>
<tr><td align="left" valign="top" width="50%" headers="d0e142 ">*RRN 299</td>
<td align="left" valign="top" width="50%" headers="d0e144 ">1 record, last record only</td>
</tr>
<tr><td align="left" valign="top" width="50%" headers="d0e142 ">*KEY 299</td>
<td align="left" valign="top" width="50%" headers="d0e144 ">299 records, 299 through 1</td>
</tr>
<tr><td align="left" valign="top" width="50%" headers="d0e142 ">*RRN 150</td>
<td align="left" valign="top" width="50%" headers="d0e144 ">150 records, 150 through 299</td>
</tr>
<tr><td align="left" valign="top" width="50%" headers="d0e142 ">*KEY 150</td>
<td align="left" valign="top" width="50%" headers="d0e144 ">150 records, 150 through 1</td>
</tr>
<tr><td colspan="2" align="left" valign="top" headers="d0e142 d0e144 "><div class="note"><span class="notetitle">Note:</span> This
column assumes only one key field for *KEY values and uses the remote file
name as the default value for the record format name.</div>
</td>
</tr>
</tbody>
</table>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbae5source36.htm" title="Before an iSeries server can access files on a System/36, Level 1.0 of the DDM architecture must be installed on the System/36. These topics contain information that applies when an iSeries server is the source or target server communicating with a System/36.">System/36 source and target considerations for DDM</a></div>
</div>
</div>
</body>
</html>