97 lines
8.8 KiB
HTML
97 lines
8.8 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="Input spooling" />
|
||
|
|
<meta name="abstract" content="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." />
|
||
|
|
<meta name="description" content="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." />
|
||
|
|
<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="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="rzakssplfileinput" />
|
||
|
|
<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>Input spooling</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzakssplfileinput"><a name="rzakssplfileinput"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Input spooling</h1>
|
||
|
|
<div><p>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.</p>
|
||
|
|
<p>The main elements of input spooling are:</p>
|
||
|
|
<ul><li><strong>Job queue</strong>: An ordered list of batch jobs submitted to the server
|
||
|
|
for running and from which batch jobs are selected to run.</li>
|
||
|
|
<li><strong>Reader</strong>: A function that takes jobs from an input device or database
|
||
|
|
file and places them on a job queue.</li>
|
||
|
|
</ul>
|
||
|
|
<p>When a batch job is read from an input source by a reader, the commands
|
||
|
|
in the input stream are stored in the server as requests for the job, the
|
||
|
|
inline data is spooled as inline data files, and an entry for the job is placed
|
||
|
|
on a job queue. The job information remains stored in the server where it
|
||
|
|
was placed by the reader until the job entry is selected from the job queue
|
||
|
|
for processing by a subsystem.</p>
|
||
|
|
<div class="p"><div class="fignone" id="rzakssplfileinput__RSLH145"><a name="rzakssplfileinput__RSLH145"><!-- --></a><span class="figcap">Figure 1. Relationship of Input Spooling Elements</span><img src="rslh145.gif" alt="Relationship of Input Spooling Elements" /></div>
|
||
|
|
</div>
|
||
|
|
<p>You can use the reader functions to read an input stream from diskette
|
||
|
|
or database files.</p>
|
||
|
|
<div class="p"><div class="fignone" id="rzakssplfileinput__RSLH116"><a name="rzakssplfileinput__RSLH116"><!-- --></a><span class="figcap">Figure 2. Typical Organization of an Input Stream</span><img src="rslh116.gif" alt="Typical Organization of an Input
Stream" /></div>
|
||
|
|
</div>
|
||
|
|
<div class="p">The job queue on which the job is placed is specified on the <span class="parmname">JOBQ</span> parameter
|
||
|
|
on the Batch Job <span class="cmdname">BCHJOB</span> command, on the Start Database
|
||
|
|
Reader<span class="cmdname">STRDBRDR</span> command, or in the job description. If the <span class="parmname">JOBQ</span> parameter
|
||
|
|
on the <span class="cmdname">BCHJOB</span> command is:<ul><li>*RDR: The job queue is selected from the JOBQ parameter on the Start database
|
||
|
|
reader (<span class="cmdname">STRDBRDR</span>) command.</li>
|
||
|
|
<li>*JOBD: The job queue is selected from the JOBQ parameter in the job description.</li>
|
||
|
|
<li>A specific job queue: The specified queue is used.</li>
|
||
|
|
</ul>
|
||
|
|
</div>
|
||
|
|
<p>For jobs with small input streams, you might improve server performance
|
||
|
|
by not using input spooling. The Submit Job (<span class="cmdname">SBMJOB</span>) command
|
||
|
|
reads the input stream and places the job on the job queue in the appropriate
|
||
|
|
subsystem, bypassing the spooling subsystem and reader operations.</p>
|
||
|
|
<p>If your job requires a large input stream to be read, you should use input
|
||
|
|
spooling (Start Diskette Reader <span class="cmdname">STRDKTRDR</span> or Start Database
|
||
|
|
Reader<span class="cmdname">STRDBRDR</span> command) to allow the job to be input independent
|
||
|
|
of when the job is actually processed.</p>
|
||
|
|
</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="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>
|