95 lines
7.4 KiB
HTML
95 lines
7.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="concept" />
|
|
<meta name="DC.Title" content="Spooled files" />
|
|
<meta name="abstract" content="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." />
|
|
<meta name="description" content="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." />
|
|
<meta name="DC.Relation" scheme="URI" content="rzataprintthis.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="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="rzatakickoff" />
|
|
<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>Spooled files</title>
|
|
</head>
|
|
<body id="rzatakickoff"><a name="rzatakickoff"><!-- --></a>
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|
<h1 class="topictitle1">Spooled files</h1>
|
|
<div><p>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.</p>
|
|
<p>A spooled file holds output data until it can be printed. The spooled file
|
|
collects data from a device until a program or device is able to process the
|
|
data. A program uses a spooled file as if it were reading from or writing
|
|
to an actual device.</p>
|
|
<p>Spooling functions help server users to manage input and output operations
|
|
more efficiently. The server supports two types of spooling, output spooling
|
|
and input spooling. Output spooling can be used for printer devices. Input
|
|
spooling applies to database file input.</p>
|
|
<p>At the end of a the job, the job log can be written to the spooled file
|
|
QPJOBLOG so that it can be printed. After the job log is written to the spooled
|
|
file, the job log is deleted.</p>
|
|
<p>For information about using spooled files with printer output, see <a href="../rzalu/rzalusplf.htm">Spooled
|
|
files</a> in the Basic Printing topic.</p>
|
|
</div>
|
|
<div>
|
|
<ul class="ullinks">
|
|
<li class="ulchildlink"><strong><a href="rzataprintthis.htm">Printable PDF</a></strong><br />
|
|
Use this to view and print a PDF of this information.</li>
|
|
<li class="ulchildlink"><strong><a href="rzaksoutputsp.htm">Output spooling</a></strong><br />
|
|
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.</li>
|
|
<li class="ulchildlink"><strong><a href="rzaksoutputq.htm">Output queues and spooled files</a></strong><br />
|
|
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.</li>
|
|
<li class="ulchildlink"><strong><a href="rzaksoutputq2.htm">Default server output queues</a></strong><br />
|
|
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.</li>
|
|
<li class="ulchildlink"><strong><a href="rzakswriter.htm">Spooling writers</a></strong><br />
|
|
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.</li>
|
|
<li class="ulchildlink"><strong><a href="rzakswriter2.htm">Summary of spooling writer commands</a></strong><br />
|
|
There are many commands that you can use to control spooling writers.</li>
|
|
<li class="ulchildlink"><strong><a href="rzaksinputsp.htm">Input spooling</a></strong><br />
|
|
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.</li>
|
|
<li class="ulchildlink"><strong><a href="rzaksinputsp2.htm">Summary of job input commands</a></strong><br />
|
|
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.</li>
|
|
<li class="ulchildlink"><strong><a href="rzaksinldf.htm">Use an inline data file</a></strong><br />
|
|
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.</li>
|
|
<li class="ulchildlink"><strong><a href="rzaksidfoc.htm">Open considerations for inline data files</a></strong><br />
|
|
The following considerations apply to opening inline data files:</li>
|
|
</ul>
|
|
</div>
|
|
</body>
|
|
</html> |