80 lines
7.2 KiB
HTML
80 lines
7.2 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="Open considerations for inline data files" />
|
||
|
|
<meta name="abstract" content="The following considerations apply to opening inline data files:" />
|
||
|
|
<meta name="description" content="The following considerations apply to opening inline data files:" />
|
||
|
|
<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="rzaksinldf.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="rzaksidfoc" />
|
||
|
|
<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>Open considerations for inline data files</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzaksidfoc"><a name="rzaksidfoc"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Open considerations for inline data files</h1>
|
||
|
|
<div><p>The following considerations apply to opening inline data files: </p>
|
||
|
|
<ul><li>Record length specifies the length of the input records. (Record length
|
||
|
|
is optional.) When the record length exceeds the length of the data, a message
|
||
|
|
is sent to your program. The data is padded with blanks. When the record length
|
||
|
|
is less than the data length, the records are truncated. </li>
|
||
|
|
<li>When a file is specified in a program, the server searches for the file
|
||
|
|
as a named inline data file before it searches for the file in a library.
|
||
|
|
Therefore, if a named inline data file has the same name as a file that is
|
||
|
|
not an inline data file, the inline data file is always used, even if the
|
||
|
|
file name is qualified by a library name. </li>
|
||
|
|
<li>Named inline data files can be shared between programs in the same job
|
||
|
|
by specifying SHARE(*YES) on a create file or override file command. For example,
|
||
|
|
if an override file command specifying a file named INPUT and SHARE(*YES)
|
||
|
|
is in a batch job with an inline data file named INPUT, any programs running
|
||
|
|
in the job that specify the file name INPUT will share the same named inline
|
||
|
|
data file. Unnamed inline data files cannot be shared between programs in
|
||
|
|
the same job.</li>
|
||
|
|
<li>When you use inline data files, you should make sure the correct file
|
||
|
|
type is specified on the //DATA command. For example, if the file is to be
|
||
|
|
used as a source file, the file type on the //DATA command must be source. </li>
|
||
|
|
<li>Inline data files must be opened for input only.</li>
|
||
|
|
</ul>
|
||
|
|
</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>
|
||
|
|
<div class="reltasks"><strong>Related tasks</strong><br />
|
||
|
|
<div><a href="rzaksinldf.htm" title="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.">Use an inline data file</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|