73 lines
4.8 KiB
HTML
73 lines
4.8 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="OUTFILE parameter considerations for DDM" />
|
||
|
|
<meta name="abstract" content="The OUTFILE parameter is used on such commands as the Display File Description (DSPFD), the Display File Field Description (DSPFFD), the Display Object Description (DSPOBJD), and the Create Auto Report Program (CRTRPTPGM). The parameter identifies a database file into which output data created by the command is stored." />
|
||
|
|
<meta name="description" content="The OUTFILE parameter is used on such commands as the Display File Description (DSPFD), the Display File Field Description (DSPFFD), the Display Object Description (DSPOBJD), and the Create Auto Report Program (CRTRPTPGM). The parameter identifies a database file into which output data created by the command is stored." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbae5clparameter.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="rbae5outfp" />
|
||
|
|
<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>OUTFILE parameter considerations for DDM</title>
|
||
|
|
</head>
|
||
|
|
<body id="rbae5outfp"><a name="rbae5outfp"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">OUTFILE parameter considerations for DDM</h1>
|
||
|
|
<div><p>The OUTFILE parameter is used on such commands as the <span class="cmdname">Display
|
||
|
|
File Description (DSPFD)</span>, the <span class="cmdname">Display File Field Description
|
||
|
|
(DSPFFD)</span>, the <span class="cmdname">Display Object Description (DSPOBJD)</span>,
|
||
|
|
and the <span class="cmdname">Create Auto Report Program (CRTRPTPGM)</span>. The parameter
|
||
|
|
identifies a database file into which output data created by the command is
|
||
|
|
stored.</p>
|
||
|
|
<div class="section"><p>When the name of a DDM file is specified on the OUTFILE parameter
|
||
|
|
of these commands, two restrictions apply:</p>
|
||
|
|
<ul><li>The remote server must be an <span class="keyword">iSeries™ server</span> or
|
||
|
|
a <span class="keyword">System/38™</span>. This is necessary
|
||
|
|
to ensure that the associated remote file has the proper format for the output
|
||
|
|
data.</li>
|
||
|
|
<li>The remote file associated with the DDM file must already exist. If the
|
||
|
|
remote file does not exist, a message is returned to the user indicating that
|
||
|
|
the remote file must exist before the function can be performed.</li>
|
||
|
|
</ul>
|
||
|
|
</div>
|
||
|
|
<div class="section"><p>If the remote file named on the OUTFILE parameter does exist and
|
||
|
|
is on an <span class="keyword">iSeries server</span> or a <span class="keyword">System/38</span>, the file will be checked for
|
||
|
|
three conditions before it can be used as an output database file to store
|
||
|
|
displayed output:</p>
|
||
|
|
<ul><li>The remote file must be a physical file.</li>
|
||
|
|
<li>The remote file must not be a model output file. That is, it cannot be
|
||
|
|
one of the model output files provided with the <span class="keyword">i5/OS™</span> operating
|
||
|
|
system which has the required format, but no data.</li>
|
||
|
|
<li>The record format name in the remote file must match the model output
|
||
|
|
file record format name. (This condition requires that the remote system be
|
||
|
|
an <span class="keyword">iSeries server</span> or a <span class="keyword">System/38</span>.)</li>
|
||
|
|
</ul>
|
||
|
|
</div>
|
||
|
|
<div class="section"><p>If all of these conditions are met, the remote file member is
|
||
|
|
cleared. (Output file members <em>must</em> be cleared before they can be used
|
||
|
|
again.) If the remote file member does not exist, it is created and the output
|
||
|
|
is stored in it.</p>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbae5clparameter.htm" title="This topic covers parameter considerations that apply to DDM-related CL commands.">DDM-related CL parameter considerations</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|