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

78 lines
5.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="CL command considerations for DDM" />
<meta name="abstract" content="Both compiled control language (CL) programs and interactively entered CL commands can refer to DDM files." />
<meta name="description" content="Both compiled control language (CL) programs and interactively entered CL commands can refer to DDM files." />
<meta name="DC.subject" content="limitations, CL, language considerations, high-level language (HLL), HLL (high-level language), SRCFILE parameter, SRCMBR parameter, control language (CL), CL (control language), control language (CL), SRCMBR parameter, CL (control language), source file requirements, control language (CL), restrictions, CL (control language), FILE parameter, DDM file, CL command considerations, accessing" />
<meta name="keywords" content="limitations, CL, language considerations, high-level language (HLL), HLL (high-level language), SRCFILE parameter, SRCMBR parameter, control language (CL), CL (control language), control language (CL), SRCMBR parameter, CL (control language), source file requirements, control language (CL), restrictions, CL (control language), FILE parameter, DDM file, CL command considerations, accessing" />
<meta name="DC.Relation" scheme="URI" content="rbae5plc.htm" />
<meta name="DC.Relation" scheme="URI" content="rbae5cldsp.htm" />
<meta name="DC.Relation" scheme="URI" content="rbae5ddmop.htm" />
<meta name="DC.Relation" scheme="URI" content="rbae5sumchts.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="rbae5clcon" />
<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>CL command considerations for DDM</title>
</head>
<body id="rbae5clcon"><a name="rbae5clcon"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">CL command considerations for DDM</h1>
<div><p>Both compiled control language (CL) programs and interactively
entered CL commands can refer to DDM files.</p>
<div class="section"><p>Generally, DDM file names can be specified in CL commands anywhere
a database file name can be specified for both <span class="keyword">iSeries™</span> and
non-<span class="keyword">iSeries</span> target servers.
But there are some limitations.</p>
</div>
<div class="section"><p>Listed here are some examples of where DDM file names
can be specified:</p>
<ul><li>DDM file names can be specified on many of the database file-related commands,
such as the copy, display, and override file commands.</li>
<li>DDM file names can be specified on the create file commands to access
remote <em>source</em> files, but only if the target server is an <span class="keyword">iSeries server</span> or
a <span class="keyword">System/38™</span>. A DDM file name
can be specified on the SRCFILE parameter, and a member name can be specified
on the SRCMBR parameter. If the remote source file referred to by the DDM
file is not on an <span class="keyword">iSeries server</span> or
a <span class="keyword">System/38</span>, an error occurs.
The considerations for remote <span class="keyword">iSeries</span> or <span class="keyword">System/38</span> source members are the same
as for local source members.</li>
<li>DDM file names can be specified on the FILE parameter of the <span class="cmdname">Declare
File (DCLF)</span> command.</li>
</ul>
</div>
<div class="section"><p>When a DDM file name is specified, some commands act on files
on the source server, some act on target files, and some parameter values
allow you to specify either a source or target file.</p>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbae5plc.htm" title="DDM is supported by these iSeries languages.">Programming language considerations for DDM</a></div>
</div>
<div class="relconcepts"><strong>Related concepts</strong><br />
<div><a href="rbae5cldsp.htm" title="This topic contains DDM-related information about specific iSeries control language (CL) commands, data description specifications (DDS) considerations, DDS keywords, and DDM user profile authority.">Use CL and DDS with DDM</a></div>
<div><a href="rbae5ddmop.htm" title="This topic provides task-oriented information and examples that describe various aspects of DDM operation considerations.">Operating considerations for DDM</a></div>
</div>
<div class="relref"><strong>Related reference</strong><br />
<div><a href="rbae5sumchts.htm" title="This topic shows summary charts containing most of the control language (CL) commands used with DDM.">DDM-related CL command summary charts</a></div>
</div>
</div>
</body>
</html>