66 lines
4.7 KiB
HTML
66 lines
4.7 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 gets done" />
|
||
|
|
<meta name="abstract" content="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." />
|
||
|
|
<meta name="description" content="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." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakswmintro.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="DC.Relation" scheme="URI" content="rzakshowwrklvs.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="rzakshowworkgetsdone" />
|
||
|
|
<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 gets done</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzakshowworkgetsdone"><a name="rzakshowworkgetsdone"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">How work gets done</h1>
|
||
|
|
<div><p>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.</p>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<ul class="ullinks">
|
||
|
|
<li class="ulchildlink"><strong><a href="rzakswhatswrk.htm">What work is</a></strong><br />
|
||
|
|
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.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzaksbfrwrkentsys.htm">What happens before work enters the system</a></strong><br />
|
||
|
|
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.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzakshowwrkgetsinsys.htm">How work enters the system</a></strong><br />
|
||
|
|
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.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzakshowwrkgetsproc.htm">How work gets processed</a></strong><br />
|
||
|
|
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. </li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzakshowwrklvs.htm">How work leaves the system</a></strong><br />
|
||
|
|
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.</li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzakswmintro.htm" title="Work management supports the commands and internal functions necessary to control system operation and the daily workload on the system. In addition, work management contains the functions that you need to distribute resources for your applications so that your system can handle your applications.">Introduction to work management</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|