67 lines
5.3 KiB
HTML
67 lines
5.3 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="What work is" />
|
||
|
|
<meta name="abstract" content="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." />
|
||
|
|
<meta name="description" content="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." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakshowworkgetsdone.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="rzakswhatswrk" />
|
||
|
|
<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>What work is</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzakswhatswrk"><a name="rzakswhatswrk"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">What work is</h1>
|
||
|
|
<div><p>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.</p>
|
||
|
|
<p>Work is done when you turn on your system, when you open a file, or when
|
||
|
|
you query a database. Each piece of work on the system is performed by a job.
|
||
|
|
A job can be as simple as an application that waits for a user to call it
|
||
|
|
or it can be as complex as a constantly running system query that monitors
|
||
|
|
the number of users on the system every hour. Some jobs, specifically batch
|
||
|
|
and interactive jobs, have job descriptions associated with them that tell
|
||
|
|
when and where the job will run.</p>
|
||
|
|
<p>Jobs are made up of programs that perform certain functions. There is no
|
||
|
|
limit to the amount of functions a job performs. A job contains the step-by-step
|
||
|
|
instructions that must be completed for work to be done. The programs that
|
||
|
|
make up the job run in a specific order. (For example, program A needs to
|
||
|
|
run before program B can begin.) Threads help a job complete
|
||
|
|
its work. An active job contains at least one thread. When a job contains
|
||
|
|
multiple threads, it has the ability to do more than one thing at once. For
|
||
|
|
example, one thread can go out and do calculations while another thread waits
|
||
|
|
for more data to process.</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="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><a href="rzakshowwrklvs.htm" title="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.">How work leaves the system</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|