63 lines
5.0 KiB
HTML
63 lines
5.0 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="How work leaves the system" />
|
||
|
|
<meta name="abstract" content="The output queue works similarly to a job queue in that it schedules output to be printed. Both the printer output and the output queue carry attributes that are used to print the information." />
|
||
|
|
<meta name="description" content="The output queue works similarly to a job queue in that it schedules output to be printed. Both the printer output and the output queue carry attributes that are used to print the information." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakshowworkgetsdone.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakswhatswrk.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksbfrwrkentsys.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakshowwrkgetsinsys.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakshowwrkgetsproc.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="rzakshowwrklvs" />
|
||
|
|
<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>How work leaves the system</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzakshowwrklvs"><a name="rzakshowwrklvs"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">How work leaves the system</h1>
|
||
|
|
<div><p>The output queue works similarly to a job queue in that it schedules
|
||
|
|
output to be printed. Both the printer output and the output queue carry attributes
|
||
|
|
that are used to print the information.</p>
|
||
|
|
<p>Printer output holds output data that is waiting to be processed, such
|
||
|
|
as information waiting to be printed. Printer output also holds important
|
||
|
|
information that is used to schedule when it will be printed. Printer output
|
||
|
|
attributes include the output queue in which the printer output will reside,
|
||
|
|
the priority, the status and the schedule of the printer output.</p>
|
||
|
|
<p>The output queue contains attributes of its own that determine the order
|
||
|
|
in which the printer output files are processed. It also contains the authority
|
||
|
|
that is needed to make changes to the printer output and the
|
||
|
|
output queue.</p>
|
||
|
|
<p>When the printer output is ready to be sent to the printer it is picked
|
||
|
|
up by a writer job. The writer job takes the data from the printer output
|
||
|
|
and prepares it to be printed.</p>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzakshowworkgetsdone.htm" title="Use this information to learn about what work is, what needs to be set up before work can begin, how work travels through the system, and what happens to work after it is done running.">How work gets done</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
||
|
|
<div><a href="rzakswhatswrk.htm" title="On the iSeries server, work is always being done, whether you initiate it or the system initiates it. Any action done on the iSeries server has some type of work being performed to complete it.">What work is</a></div>
|
||
|
|
<div><a href="rzaksbfrwrkentsys.htm" title="All jobs, with the exception of system jobs, run within subsystems. For work to start in an active subsystem, memory pools and at least one source of work entry point need to be established. Job queues are an example of a source of work.">What happens before work enters the system</a></div>
|
||
|
|
<div><a href="rzakshowwrkgetsinsys.htm" title="Work entries identify the sources where jobs enter a subsystem to become available to run. Each type of job on the iSeries has different types of work entries that it uses.">How work enters the system</a></div>
|
||
|
|
<div><a href="rzakshowwrkgetsproc.htm" title="When the iSeries server is started, a subsystem monitor job begins running. The subsystem monitor job controls the jobs within subsystems. It also starts and ends work, as well as manages the resources for work in the subsystem.">How work gets processed</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|