66 lines
5.2 KiB
HTML
66 lines
5.2 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="A job's life: the job enters the subsystem" />
|
|
<meta name="abstract" content="Subsystems are operating environments where the system manages the resources that jobs use and controls the jobs that run within them. After jobs are running in the subsystem, the subsystem job carries out user requests on a job such as holding, releasing, and ending a job. When the job enters the subsystem it becomes active." />
|
|
<meta name="description" content="Subsystems are operating environments where the system manages the resources that jobs use and controls the jobs that run within them. After jobs are running in the subsystem, the subsystem job carries out user requests on a job such as holding, releasing, and ending a job. When the job enters the subsystem it becomes active." />
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksjoblife.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksjoblifejobq.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksjoblifemp.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="rzaksjoblifesbs" />
|
|
<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>A job's life: the job enters the subsystem</title>
|
|
</head>
|
|
<body id="rzaksjoblifesbs"><a name="rzaksjoblifesbs"><!-- --></a>
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|
<h1 class="topictitle1">A job's life: the job enters the subsystem</h1>
|
|
<div><p> <dfn class="term">Subsystems</dfn> are operating environments where the system
|
|
manages the resources that jobs use and controls the jobs that run within
|
|
them. After jobs are running in the subsystem, the subsystem job carries out
|
|
user requests on a job such as holding, releasing, and ending a job. When
|
|
the job enters the subsystem it becomes active.</p>
|
|
<p>Like jobs, subsystems have descriptions that carry important information
|
|
needed to complete the work. In the subsystem description is the routing entry.
|
|
The <dfn class="term">routing entry</dfn> references the class object, which contains
|
|
the attributes that control the run-time environment. However, before the
|
|
job can get its routing entry, the routing data must make a match with a compare
|
|
value in the routing entry. If this association is not made, the job will
|
|
not run. </p>
|
|
<p>After the association between the routing data and the routing entry is
|
|
made, the class object the job will use is determined. Some of the attributes
|
|
that control the run-time environment include the run priority, the time slice,
|
|
the maximum wait time, the maximum processing time, the maximum temporary
|
|
storage, and the maximum number of threads. </p>
|
|
<p>The subsystem description defines the memory pools that will be allocated
|
|
to the subsystem. The subsystem description also contains the maximum active
|
|
jobs, which is the maximum number of active jobs at one time in the subsystem. </p>
|
|
<p>Until a job gets its activity level and is assigned a memory pool, it cannot
|
|
run. The subsystem description, like the job description, carries information,
|
|
such as the memory pool to use, the routing entry, the maximum active jobs,
|
|
and the number of active jobs currently in the subsystem. </p>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaksjoblife.htm" title="To understand the basics of iSeries work management, follow a simple batch job as it moves through the system.">A job's life</a></div>
|
|
<div class="previouslink"><strong>Previous topic:</strong> <a href="rzaksjoblifejobq.htm" title="Job queues are work entry points for batch jobs to enter the system. They can be thought of as "waiting rooms" for a subsystem.">A job's life: the job enters the job queue</a></div>
|
|
<div class="nextlink"><strong>Next topic:</strong> <a href="rzaksjoblifemp.htm" title="Memory is a resource from the memory pool that the subsystem uses to run the job. The amount of memory in a memory pool, as well as how many other jobs are competing for memory, affect how efficiently a job runs.">A job's life: the subsystem uses memory from the memory pool to run the job</a></div>
|
|
</div>
|
|
</div>
|
|
</body>
|
|
</html> |