91 lines
6.7 KiB
HTML
91 lines
6.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="concept" />
|
|
<meta name="DC.Title" content="Write the output from a command directly to a database file" />
|
|
<meta name="abstract" content="You can store the output from many control language (CL) commands in an output physical file by specifying the OUTFILE parameter on the commands. You can then use the output files in programs or utilities (for example, Query) for data analysis." />
|
|
<meta name="description" content="You can store the output from many control language (CL) commands in an output physical file by specifying the OUTFILE parameter on the commands. You can then use the output files in programs or utilities (for example, Query) for data analysis." />
|
|
<meta name="DC.subject" content="writing, output from a command directly to a database file, command, writing output directly to a database file, database file, writing the output from a command to, OUTFILE parameter, parameter, OUTFILE, output file, for CL commands" />
|
|
<meta name="keywords" content="writing, output from a command directly to a database file, command, writing output directly to a database file, database file, writing the output from a command to, OUTFILE parameter, parameter, OUTFILE, output file, for CL commands" />
|
|
<meta name="DC.Relation" scheme="URI" content="rbafoxreff.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rbafourfof.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rbafooutpr.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rbafomdljrn.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rbafodspprb.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="../rbam6/rbam6clmain.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="../cl/dspffd.htm" />
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 1998, 2006" />
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 1998, 2006" />
|
|
<meta name="DC.Format" content="XHTML" />
|
|
<meta name="DC.Identifier" content="rbafofrfof" />
|
|
<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> Write the output from a command directly to a database file</title>
|
|
</head>
|
|
<body id="rbafofrfof"><a name="rbafofrfof"><!-- --></a>
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|
<h1 class="topictitle1"> Write the output from a command directly to a database file</h1>
|
|
<div><p>You can store the output from many control language (CL) commands
|
|
in an output physical file by specifying the OUTFILE parameter on the commands.
|
|
You can then use the output files in programs or utilities (for example, Query)
|
|
for data analysis.</p>
|
|
<p> For example, you can send the output of the Display Program References
|
|
(DSPPGMREF) command to a physical file, then query that file to determine
|
|
which programs use a specific file.</p>
|
|
<p>The physical files are created for you when you specify the OUTFILE parameter
|
|
on the commands. Initially, the files are created with private authority;
|
|
only the owner (the person who ran the command) can use it. However, the owner
|
|
can authorize other users to these files as you would for any other database
|
|
file.</p>
|
|
<div class="p">The system supplies model files that identify the record format for each
|
|
command that can specify the OUTFILE parameter. If you specify a file name
|
|
on the OUTFILE parameter for a file that does not already exist, the system
|
|
creates the file using the same record format as the model file. If you specify
|
|
a file name for an existing output file, the system checks to see if the record
|
|
format is the same record format as the model file. If the record formats
|
|
do not match, the system sends a message to the job and the command does not
|
|
complete. <div class="note"><span class="notetitle">Note:</span> You must use your own files for output files, rather than
|
|
specifying the system-supplied model files on the OUTFILE parameter.</div>
|
|
</div>
|
|
<div class="p">See the Control language (CL) topic for a list of commands
|
|
that allow output files and the names of the model files supplied for those
|
|
commands. <div class="note"><span class="notetitle">Note:</span> All system-supplied model files are located in the QSYS library.</div>
|
|
</div>
|
|
<p>You can display the fields contained in the record formats of the system-supplied
|
|
model files using the Display File Field Descriptions (DSPFFD) command.</p>
|
|
</div>
|
|
<div>
|
|
<ul class="ullinks">
|
|
<li class="ulchildlink"><strong><a href="rbafourfof.htm">Example: A command output file</a></strong><br />
|
|
This example shows how to write the output from a control language (CL) command directly to a database file.</li>
|
|
<li class="ulchildlink"><strong><a href="rbafooutpr.htm">Output files for the Display File Description (DSPFD) command</a></strong><br />
|
|
The Display File Description (DSPFD) command provides unique output files, depending on the parameters specified.</li>
|
|
<li class="ulchildlink"><strong><a href="rbafomdljrn.htm">Output files for the Display Journal (DSPJRN) command</a></strong><br />
|
|
The Display Journal (DSPJRN) command provides unique output files.</li>
|
|
<li class="ulchildlink"><strong><a href="rbafodspprb.htm">Output files for the Display Problem (DSPPRB) command</a></strong><br />
|
|
The Display Problem (DSPPRB) command provides unique output files, depending on the type of record.</li>
|
|
</ul>
|
|
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbafoxreff.htm" title="The iSeries integrated database provides file attribute and cross-reference information.">Use database attribute and cross-reference information</a></div>
|
|
</div>
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
|
<div><a href="../rbam6/rbam6clmain.htm">Control language (CL)</a></div>
|
|
</div>
|
|
<div class="relref"><strong>Related reference</strong><br />
|
|
<div><a href="../cl/dspffd.htm">Display File Field Description (DSPFFD) command</a></div>
|
|
</div>
|
|
</div>
|
|
</body>
|
|
</html> |