89 lines
6.7 KiB
HTML
89 lines
6.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="Concepts" />
|
||
|
|
<meta name="abstract" content="Whether you are new to work management or have been using work management tools for years, you will find something useful in the Concepts section of the Work management topic collection." />
|
||
|
|
<meta name="description" content="Whether you are new to work management or have been using work management tools for years, you will find something useful in the Concepts section of the Work management topic collection." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaks1.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakssystemstructure.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksaboutsbs.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksaboutmempools.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksaboutjobs.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksschedulejobs.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksaboutjobqueue.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksoutputstructure.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksjoblogs.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksjaabout.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="rzaksconcepts" />
|
||
|
|
<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>Concepts</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzaksconcepts"><a name="rzaksconcepts"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Concepts</h1>
|
||
|
|
<div><p>Whether you are new to work management or have been using work
|
||
|
|
management tools for years, you will find something useful in the Concepts
|
||
|
|
section of the Work management topic collection.</p>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<ul class="ullinks">
|
||
|
|
<li class="ulchildlink"><strong><a href="rzakssystemstructure.htm">The structure of your system</a></strong><br />
|
||
|
|
You have just received your iSeries™. It is unpacked and you're ready
|
||
|
|
to go - or are you? What subsystems are shipped with the system?
|
||
|
|
Are there any start-up programs that you need to change? What kind of user
|
||
|
|
interface can you expect to work with?</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzaksaboutsbs.htm">Subsystems</a></strong><br />
|
||
|
|
The subsystem is where work is processed on the iSeries™ server.
|
||
|
|
A subsystem is a single, predefined operating environment through which the
|
||
|
|
system coordinates the work flow and resource use. The system can contain
|
||
|
|
several subsystems, all operating independently of each other. Subsystems
|
||
|
|
manage resources. </li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzaksaboutmempools.htm">Memory pools</a></strong><br />
|
||
|
|
A memory pool is a logical division of main memory or storage that
|
||
|
|
is reserved for processing a job or group of jobs. On the iSeries™ server,
|
||
|
|
all main storage can be divided into logical allocations called memory pools.
|
||
|
|
By default, the system manages the transfer of data and programs into memory
|
||
|
|
pools.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzaksaboutjobs.htm">Jobs</a></strong><br />
|
||
|
|
All work done on a system is performed through jobs. Each job has a unique name within the system. All jobs, with the exception of system jobs, run within subsystems. A job can enter the subsystem from any of the work entries, such as a job queue entry, workstation entry, communications entry, autostart job entry, or prestart job entry.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzaksschedulejobs.htm">Job scheduling options</a></strong><br />
|
||
|
|
The job schedule function allows for time-dependent scheduling
|
||
|
|
of iSeries™ batch
|
||
|
|
jobs. You can schedule jobs to be released from the job queue at a particular
|
||
|
|
time, or you can use a job schedule entry to submit your job to the job queue
|
||
|
|
automatically at the time you specify. Job scheduling allows you to control
|
||
|
|
the date and time a batch job is submitted to or becomes eligible to start
|
||
|
|
from a job queue. This flexibility can help you as you balance the work load
|
||
|
|
on your system.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzaksaboutjobqueue.htm">Job queues</a></strong><br />
|
||
|
|
A job queue contains an ordered list of jobs waiting to be processed by a subsystem. The job queue is the first place that a submitted batch job goes before becoming active in a subsystem. The job is held here until a number of factors are met.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzaksoutputstructure.htm">Output queues</a></strong><br />
|
||
|
|
Output queues are areas where printer output files (also called spooled files) wait to be processed and sent to the printer. Printer output is created either by the system or by the user using a print file.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzaksjoblogs.htm">Job logs</a></strong><br />
|
||
|
|
A job log contains information related to requests entered for a job. A job log has two forms, a pending form and a spooled form.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzaksjaabout.htm">Job accounting</a></strong><br />
|
||
|
|
The job accounting function gathers data so that you can determine who is using your system and what system resources they are using. It also assists you in evaluating the overall use of your system. Job accounting is optional. You must take specific steps to set up job accounting. You can request the system to gather job resource accounting data, printer file accounting data, or both. You can also assign accounting codes to user profiles or specific jobs.</li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaks1.htm" title="Work management is an important building block within the iSeries server operating system.">Work management</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|