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

62 lines
4.1 KiB
HTML
Raw Permalink Normal View History

2024-04-02 14:02:31 +00:00
<?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="Non-iSeries target considerations for DDM" />
<meta name="abstract" content="DDS can be used with a non-iSeries file only if the local iSeries program is compiled using a local iSeries file that has the same record format name as the DDM file being used." />
<meta name="description" content="DDS can be used with a non-iSeries file only if the local iSeries program is compiled using a local iSeries file that has the same record format name as the DDM file being used." />
<meta name="DC.subject" content="target DDM (TDDM), non-, server, iSeries, considerations" />
<meta name="keywords" content="target DDM (TDDM), non-, server, iSeries, considerations" />
<meta name="DC.Relation" scheme="URI" content="rbae5ddsinfo.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="rbae5nontargetconsiderations" />
<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>Non-iSeries target considerations
for DDM</title>
</head>
<body id="rbae5nontargetconsiderations"><a name="rbae5nontargetconsiderations"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">Non-<span class="keyword">iSeries</span> target considerations
for DDM</h1>
<div><p>DDS can be used with a non-<span class="keyword">iSeries™</span> file
only if the local <span class="keyword">iSeries</span> program
is compiled using a local <span class="keyword">iSeries</span> file
that has the same record format name as the DDM file being used.</p>
<div class="section"><p>After the program is compiled, the local file can be overridden
by a DDM file that accesses the remote file. LVLCHK(*NO) must be specified
in the DDM file or in an OVRDBF command.</p>
</div>
<div class="section"><p>If no DDS exists on the local server to describe the remote file,
the program must describe the fields. The <span class="cmdname">Display File Field Description
(DSPFFD)</span> command can be used to display the field attributes of
the remote file. LVLCHK(*NO) should be specified in the DDM file or in an <span class="cmdname">OVRDBF</span> command.</p>
</div>
<div class="section"><p>If LVLCHK(*RMTFILE) is specified or assumed, the program must
be compiled (or recompiled) using a DDM file that accesses the remote file.
The <span class="keyword">iSeries server</span> then creates a
record format and fields for the remote file. The names of the fields that
are created are of the type K<em>nnnnn</em> for keyed fields and F<em>nnnnn</em> for
nonkeyed fields.</p>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbae5ddsinfo.htm" title="Data description specifications (DDS), which is used to externally describe the fields and record formats, can also be used with DDM to describe the file and record formats of a remote file.">Data description specifications considerations for DDM</a></div>
</div>
</div>
</body>
</html>