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

76 lines
5.9 KiB
HTML
Raw 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="PL/I considerations for DDM" />
<meta name="abstract" content="Compiled programs can refer to DDM files. In addition, DDM file names can be specified on the Create PL/I Program (CRTPLIPGM) command." />
<meta name="description" content="Compiled programs can refer to DDM files. In addition, DDM file names can be specified on the Create PL/I Program (CRTPLIPGM) command." />
<meta name="DC.subject" content="limitations, language considerations, high-level language (HLL), HLL (high-level language), SRCFILE parameter, SRCMBR parameter, %INCLUDE statement, command, CRTPLIPGM (Create PL/I Language Program), Create PL/I Language Program (CRTPLIPGM), command, CL, CRTPLIPGM (Create PL/I Language Program), Create PL/I Language Program (CRTPLIPGM), language program, creating, PL/I, source file requirements, restrictions, SRCMBR parameter, SRCFILE parameter, DDM file, considerations, accessing, I/O operation, operation, input/output" />
<meta name="keywords" content="limitations, language considerations, high-level language (HLL), HLL (high-level language), SRCFILE parameter, SRCMBR parameter, %INCLUDE statement, command, CRTPLIPGM (Create PL/I Language Program), Create PL/I Language Program (CRTPLIPGM), command, CL, CRTPLIPGM (Create PL/I Language Program), Create PL/I Language Program (CRTPLIPGM), language program, creating, PL/I, source file requirements, restrictions, SRCMBR parameter, SRCFILE parameter, DDM file, considerations, accessing, I/O operation, operation, input/output" />
<meta name="DC.Relation" scheme="URI" content="rbae5plc.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="rbae5plicon" />
<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>PL/I considerations for DDM</title>
</head>
<body id="rbae5plicon"><a name="rbae5plicon"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">PL/I considerations for DDM</h1>
<div><p>Compiled programs can refer to DDM files. In addition, DDM file
names can be specified on the <span class="cmdname">Create PL/I Program (CRTPLIPGM)</span> command. </p>
<div class="section"><ul><li>A DDM file name can be specified on the SRCFILE parameter, and a member
name can be specified on the SRCMBR parameter, but only if the remote source
file is on an <span class="keyword">iSeries™ server</span> or a <span class="keyword">System/38™</span>. The same is true for specifying
DDM file and member names on the %INCLUDE source directive statement. If the
remote 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
if a DDM file name is specified on the CRTPLIPGM command or %INCLUDE statement.</li>
<li>When a DDM file is accessed as the source file for a program, the margins
used in the compilation of the source are the default values of 2 and 72.
No other margin values can be specified.</li>
<li>If a %INCLUDE DDS directive statement specifies the name of a DDM file,
the record descriptions of the remote file are included in the compiled program.
However, if the remote file is not on an <span class="keyword">iSeries server</span> or
a <span class="keyword">System/38</span>, the field declares
for the record descriptions do not have meaningful names. Instead, all of
the field names are declared as F<em>nnnnn</em> and the key fields are declared
as K<em>nnnnn</em>.</li>
</ul>
</div>
<div class="section"><p>A DDM file can be used to refer to remote record files or remote
stream files. When a program opens a DDM file on the source server, the
following types of statements can be used to perform I/O operations on the
remote file at the target server, for both <span class="keyword">iSeries</span> and
non-<span class="keyword">iSeries</span> targets: OPEN,
CLOSE, READ, WRITE, REWRITE, and DELETE statements for processing record files,
and GET and PUT statements for processing stream files.</p>
</div>
<div class="section"><p>Another consideration is if the target server is not an <span class="keyword">iSeries server</span> or a <span class="keyword">System/38</span>,
the POSITION parameter on a keyed READ statement to read from a remote file
does not work if a value of NXTEQL, PRVEQL, NXTUNQ, or PRVUNQ is specified
for the parameter. (The values of NEXT, PREVIOUS, FIRST, and LAST do work.)
All the values are valid if the target system is an <span class="keyword">iSeries server</span> or
a <span class="keyword">System/38</span>.</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>
</body>
</html>