ibm-information-center/dist/eclipse/plugins/i5OS.ic.rzata_5.4.0.1/rzaksinputsp.htm

77 lines
5.7 KiB
HTML
Raw Normal View History

2024-04-02 14:02:31 +00:00
<?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="rzatakickoff.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&#xA;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="rzatakickoff.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>
</body>
</html>