64 lines
4.1 KiB
HTML
64 lines
4.1 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="iSeries target considerations for DDM" />
|
||
|
|
<meta name="abstract" content="This topic covers target considerations for DDM." />
|
||
|
|
<meta name="description" content="This topic covers target considerations for DDM." />
|
||
|
|
<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="rbae5targetconsiderations" />
|
||
|
|
<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>iSeries target considerations
|
||
|
|
for DDM</title>
|
||
|
|
</head>
|
||
|
|
<body id="rbae5targetconsiderations"><a name="rbae5targetconsiderations"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1"><span class="keyword">iSeries</span> target considerations
|
||
|
|
for DDM</h1>
|
||
|
|
<div><p>This topic covers target considerations for DDM.</p>
|
||
|
|
<div class="section"><p>As with any database file, DDS might or might not be used to externally
|
||
|
|
describe the attributes of the remote file when it is created on the remote <span class="keyword">iSeries™ server</span>. If DDS is used, then the source
|
||
|
|
server program uses those attributes when it accesses the remote file (by
|
||
|
|
using the DDM file). If DDS is not used, then the file's attributes must be
|
||
|
|
described in the program.</p>
|
||
|
|
</div>
|
||
|
|
<div class="section"><p>When a source server program that accesses a file on a target <span class="keyword">iSeries server</span> is compiled (or recompiled),
|
||
|
|
the existing DDM file is used to establish communications with the target
|
||
|
|
server, and the remote file is actually accessed during compilation to extract
|
||
|
|
its file and record attributes. Whether DDS is used to describe the file or
|
||
|
|
not, level check identifiers are created during compilation and are included
|
||
|
|
in the compiled program. These values are then used when the program is run
|
||
|
|
and LVLCHK(*RMTFILE) is in effect for the DDM file.</p>
|
||
|
|
</div>
|
||
|
|
<div class="section"><p>Whether DDS is used to describe a remote <span class="keyword">iSeries</span> file or not, a source server
|
||
|
|
program can have its own field and record format definitions provided in the
|
||
|
|
program, or the program can substitute the definitions of another source server
|
||
|
|
file that is created using DDS. Either can be done if LVLCHK(*NO) is in effect
|
||
|
|
in the DDM file or specified in an <span class="cmdname">Override with Database File (OVRDBF)</span> command
|
||
|
|
used at program run time. LVLCHK(*NO) need only be used when
|
||
|
|
the record format used on the source server is different than that of the
|
||
|
|
remote <span class="keyword">iSeries</span> file.</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>
|