99 lines
8.6 KiB
HTML
99 lines
8.6 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 queues and spooled files" />
|
||
|
|
<meta name="abstract" content="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." />
|
||
|
|
<meta name="description" content="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." />
|
||
|
|
<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="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="rzaksoutputqueuenspool" />
|
||
|
|
<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 queues and spooled files</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzaksoutputqueuenspool"><a name="rzaksoutputqueuenspool"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Output queues and spooled files</h1>
|
||
|
|
<div><p>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.</p>
|
||
|
|
<p>When a spooled file is created, the file is placed on an output queue.
|
||
|
|
Each output queue contains an ordered list of spooled files. A job can have
|
||
|
|
spooled files on one or more output queues. All spooled files on a particular
|
||
|
|
output queue should have a common set of output attributes, such as device,
|
||
|
|
form type, and lines per inch. Using common attributes on an output queue
|
||
|
|
reduces the amount of intervention required and increases the device throughput.</p>
|
||
|
|
<div class="p">The following lists some of the parameters on the Create Output Queue (<span class="cmdname">CRTOUTQ</span>)
|
||
|
|
command and what they specify:<ul><li><span class="parmname">MAXPAGES</span>: Specifies the maximum spooled file size
|
||
|
|
in pages that is allowed to be printed between a starting and ending time
|
||
|
|
of day.</li>
|
||
|
|
<li><span class="parmname">AUTOSTRWTR</span>: Specifies the number of writers that
|
||
|
|
are started automatically to this output queue.</li>
|
||
|
|
<li><span class="parmname">DSPDTA</span>: Whether users without any special authority
|
||
|
|
but who do have *USE authority to the output queue can display, copy, or send
|
||
|
|
the contents of spooled files other than their own. By specifying *OWNER for
|
||
|
|
DSPDTA, only the owner of the file or a user with *SPLCTL special authority
|
||
|
|
can display, copy, or send a file.</li>
|
||
|
|
<li><span class="parmname">JOBSEP</span>: How many, if any, job separator pages are
|
||
|
|
to be printed between the output of each job when the output is printed.</li>
|
||
|
|
<li><span class="parmname">DTAQ</span>: The data queue associated with this output
|
||
|
|
queue. If specified, an entry is sent to the data queue whenever a spooled
|
||
|
|
file goes to Ready Status on the queue.</li>
|
||
|
|
<li><span class="parmname">OPRCTL</span>: Whether a user having job control authority
|
||
|
|
can control the output queue (for example, if the user can hold the output
|
||
|
|
queue).</li>
|
||
|
|
<li><span class="parmname">SEQ</span>: Controls the order in which spooled files will
|
||
|
|
be sorted on the output queue. </li>
|
||
|
|
<li><span class="parmname">AUTCHK</span>: Specifies what type of authority to the output
|
||
|
|
queue will enable a user to control the spooled files on the output queue
|
||
|
|
(for example, enable the user to hold the spooled files on the output queue).</li>
|
||
|
|
<li><span class="parmname">AUT</span>: Public authority. Specifies what control users
|
||
|
|
have over the output queue itself.</li>
|
||
|
|
<li><span class="parmname">TEXT</span>: Text description. Up to 50 characters of text
|
||
|
|
that describes the output queue.</li>
|
||
|
|
</ul>
|
||
|
|
</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="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>
|