112 lines
9.4 KiB
HTML
112 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="concept" />
|
||
|
|
<meta name="DC.Title" content="Output spooling" />
|
||
|
|
<meta name="abstract" content="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." />
|
||
|
|
<meta name="description" content="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." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksspoolfileabout.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="rzakssplfileoutput" />
|
||
|
|
<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>Output spooling</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzakssplfileoutput"><a name="rzakssplfileoutput"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Output spooling</h1>
|
||
|
|
<div><p>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. </p>
|
||
|
|
<p>Additionally, output spooling allows the server to produce output on multiple
|
||
|
|
output devices, such as printer and diskette devices, in an efficient manner.
|
||
|
|
It does this by sending the output of a job destined for a printer to disk
|
||
|
|
storage. This process breaks a potential job limitation imposed by the availability
|
||
|
|
or speed of the output devices.</p>
|
||
|
|
<p>The main elements of output spooling are:</p>
|
||
|
|
<ul><li><strong>Device description:</strong> A description of the printer device.</li>
|
||
|
|
<li><strong>Spooled file:</strong> A file containing spooled output records that are
|
||
|
|
to be processed on an output device.</li>
|
||
|
|
<li><strong>Output queue:</strong> An ordered list of spooled files.</li>
|
||
|
|
<li><strong>Writer:</strong> A program that sends files from an output queue to a device.</li>
|
||
|
|
<li><strong>Application program:</strong> A high-level language program that creates
|
||
|
|
a spooled file using a device file with the spooling attribute specified as
|
||
|
|
SPOOL(*YES).</li>
|
||
|
|
<li><strong>Device file:</strong> A description of the format of the output, and a list
|
||
|
|
of attributes that describe how the server should process the spooled file.</li>
|
||
|
|
</ul>
|
||
|
|
<p>Output spooling functions are performed by the server without requiring
|
||
|
|
any special operations by the program that produces the output. When a device
|
||
|
|
file is opened by a program, the operating system determines whether the output
|
||
|
|
is to be spooled. When a printer file specifying spooling is opened, the spooled
|
||
|
|
file containing the output of the program is placed on the appropriate output
|
||
|
|
queue in the server.</p>
|
||
|
|
<p>A spooled file can be made available for printing when the printer file
|
||
|
|
is opened, when the printer file is closed, or at the end of the job. A printer
|
||
|
|
writer is started in the spooling subsystem to send the records to the printer.
|
||
|
|
The spooled file is selected from an output queue. </p>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Spooling device descriptions</h4><p>Device descriptions
|
||
|
|
must be created for each printer and diskette device in order to define that
|
||
|
|
device to the server. Printer device descriptions are created using the Create
|
||
|
|
Device Description for Printer (<span class="cmdname">CRTDEVPRT</span>) command; diskette
|
||
|
|
device descriptions are created using the Create Device Description for Diskette
|
||
|
|
(<span class="cmdname">CRTDEVDKT</span>) command.</p>
|
||
|
|
</div>
|
||
|
|
<div class="section"><h4 class="sectiontitle">File redirection of spooled files</h4><p>File redirection
|
||
|
|
occurs when a spooled file is sent to an output device other than the one
|
||
|
|
for which it was originally intended. File redirection can involve devices
|
||
|
|
that process different media (such as printer output sent to a diskette device)
|
||
|
|
or devices that process the same type of media but are of different devices
|
||
|
|
types (such as 5219 Printer output sent to a 4224 Printer).</p>
|
||
|
|
<p>Depending
|
||
|
|
on the new output device for the spooled file, the file can be
|
||
|
|
processed just as it would have been on the originally specified device. However,
|
||
|
|
differences in devices often cause the output to be formatted differently.
|
||
|
|
In these cases, the server sends an inquiry message to the writer's message
|
||
|
|
queue to inform you of the situation and allow you to specify whether you
|
||
|
|
want printing to continue. </p>
|
||
|
|
<p></p>
|
||
|
|
</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="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 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>
|