114 lines
9.4 KiB
HTML
114 lines
9.4 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="task" />
|
|
<meta name="DC.Title" content="Use an inline data file" />
|
|
<meta name="abstract" content="An inline data file is a data file that is included as part of a batch job when the job is read by a reader or a submit jobs command. You use SBMDBJOB or STRDBRDR to queue up a CL batch stream (stream of CL commands to be executed or run). That CL batch stream can include data to be placed into "temporary" files (inline files). When the job ends, the inline files are deleted." />
|
|
<meta name="description" content="An inline data file is a data file that is included as part of a batch job when the job is read by a reader or a submit jobs command. You use SBMDBJOB or STRDBRDR to queue up a CL batch stream (stream of CL commands to be executed or run). That CL batch stream can include data to be placed into "temporary" files (inline files). When the job ends, the inline files are deleted." />
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksspoolfileabout.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksoutputsp.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksoutputq.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksoutputq2.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakswriter.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakswriter2.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksinputsp.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksinputsp2.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksidfoc.htm" />
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 2004-2006" />
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 2004-2006" />
|
|
<meta name="DC.Format" content="XHTML" />
|
|
<meta name="DC.Identifier" content="rzaksinldf" />
|
|
<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>Use an inline data file</title>
|
|
</head>
|
|
<body id="rzaksinldf"><a name="rzaksinldf"><!-- --></a>
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|
<h1 class="topictitle1">Use an inline data file</h1>
|
|
<div><p>An inline data file is a data file that is included as part of
|
|
a batch job when the job is read by a reader or a submit jobs command. You
|
|
use <span class="cmdname">SBMDBJOB</span> or <span class="cmdname">STRDBRDR</span> to queue up
|
|
a CL batch stream (stream of CL commands to be executed or run). That CL
|
|
batch stream can include data to be placed into "temporary" files (inline
|
|
files). When the job ends, the inline files are deleted.</p>
|
|
<div class="section">An inline data file is delimited in the job by a <span class="cmdname">//DATA </span> command
|
|
at the start of the file and by an end-of-data delimiter at the end of the
|
|
file. <div class="p">The end-of-data delimiter can be a user-defined character string
|
|
or the default of //. The // must appear in positions 1 and 2. If your data
|
|
contains a // in positions 1 and 2, you should use a unique set of characters
|
|
such as: // *** END OF DATA To specify this as a unique end-of-data delimiter,
|
|
the <span class="parmname">ENDCHAR</span> parameter on the <span class="cmdname">//DATA</span> command
|
|
should be coded as: <blockquote><pre>ENDCHAR('// *** END OF DATA') </pre>
|
|
</blockquote>
|
|
<div class="note"><span class="notetitle">Note:</span> Inline
|
|
data files can be accessed only during the first routing step of a batch job.
|
|
If a batch job contains a Transfer Job (<span class="cmdname">TFRJOB</span>), a Reroute
|
|
Job (<span class="cmdname">RRTJOB</span>), or a Transfer Batch Job (<span class="cmdname">TFRBCHJOB</span>)
|
|
command, the inline data files cannot be accessed in the new routing step.</div>
|
|
</div>
|
|
<p>An
|
|
inline data file can be either named or unnamed. For an unnamed inline data
|
|
file, either QINLINE is specified as the file name in the<span class="cmdname"> //DATA</span> command
|
|
or no name is specified. For a named inline data file, a file name is specified. </p>
|
|
<div class="p">A
|
|
named inline data file has the following characteristics: <ul><li>It has a unique name in a job. No other inline data file can have the
|
|
same name. </li>
|
|
<li>It can be used more than once in a job. </li>
|
|
<li>Each time it is opened, it is positioned to the first record. </li>
|
|
</ul>
|
|
</div>
|
|
<p>To use a named inline data file, you must either specify the file
|
|
name in the program or use an override command to change the file name specified
|
|
in the program to the name of the inline data file. The file must be opened
|
|
for input only.</p>
|
|
<div class="p">An unnamed inline data file has the following characteristics:<ul><li>Its name is QINLINE. (In a batch job, all unnamed inline data files are
|
|
given the same name.) </li>
|
|
<li>It can only be used once in a job. </li>
|
|
<li>When more than one unnamed inline data file is included in a job, the
|
|
files must be in the input stream in the same order as when the files are
|
|
opened. </li>
|
|
</ul>
|
|
</div>
|
|
<div class="p">To use an unnamed inline data file, do one of the following:<ul><li>Specify QINLINE in the program. </li>
|
|
<li>Use an override file command to change the file name specified in the
|
|
program to QINLINE.</li>
|
|
</ul>
|
|
</div>
|
|
<div class="p">If your high-level language requires unique file names within
|
|
one program, you can use QINLINE as a file name only once. If you need to
|
|
use more than one unnamed inline data file, you can use an override file command
|
|
in the program to specify QINLINE for additional unnamed inline data files.
|
|
<div class="note"><span class="notetitle">Note:</span> If you run commands conditionally and process more than one unnamed
|
|
inline data file, the results cannot be predicted if the wrong unnamed inline
|
|
data file is used. </div>
|
|
</div>
|
|
</div>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaksspoolfileabout.htm" title="Spooling is a system function that saves data for later processing or printing. This data is stored in a spooled file. Spooled files work in a similar manner to tape files or other device files. Spooled files allow you to manage your data targeted for externally attached devices such as a printer.">Spooled files</a></div>
|
|
</div>
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
|
<div><a href="rzaksoutputsp.htm" title="Output spooling can be used for both printer and diskette devices. Output spooling sends job output to disk storage instead of sending it directly to a printer or diskette output device. Output spooling allows the job that produces the output to continue processing without consideration for the speed or availability of output devices.">Output spooling</a></div>
|
|
<div><a href="rzaksoutputq.htm" title="Batch and interactive job processing can result in spooled output records that are to be processed on an output device, such as a printer or diskette drive. These output records are stored in spooled files until they can be processed. There can be many spooled files for a single job.">Output queues and spooled files</a></div>
|
|
<div><a href="rzaksoutputq2.htm" title="The server is shipped with the defaults on commands to use the default output queue for the server printer as the default output queue for all spooled output. The server printer is defined by the QPRTDEV server value.">Default server output queues</a></div>
|
|
<div><a href="rzakswriter.htm" title="A writer is an i5/OS program that takes spooled files from an output queue and produces them on an output device. The spooled files that have been placed on a particular output queue will remain stored in the server until a writer is started to the output queue.">Spooling writers</a></div>
|
|
<div><a href="rzakswriter2.htm" title="There are many commands that you can use to control spooling writers.">Summary of spooling writer commands</a></div>
|
|
<div><a href="rzaksinputsp.htm" title="Input spooling takes the information from the input device, prepares the job for scheduling, and places an entry in a job queue. Using input spooling, you can typically shorten job run time, increase the number of jobs that can be run sequentially, and improve device throughput.">Input spooling</a></div>
|
|
<div><a href="rzaksinputsp2.htm" title="The following commands may be used when submitting jobs to the server. The start reader commands may be used for spooling job input; the submit job commands do not use spooling. For detailed descriptions of these commands, see the CL topic in the iSeries Information Center.">Summary of job input commands</a></div>
|
|
<div><a href="rzaksidfoc.htm" title="The following considerations apply to opening inline data files:">Open considerations for inline data files</a></div>
|
|
</div>
|
|
</div>
|
|
</body>
|
|
</html> |