116 lines
7.6 KiB
HTML
116 lines
7.6 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="Your system as a business" />
|
||
<meta name="abstract" content="To make grasping the overall concept of work management easier, try comparing your system with a business." />
|
||
<meta name="description" content="To make grasping the overall concept of work management easier, try comparing your system with a business." />
|
||
<meta name="DC.Relation" scheme="URI" content="rzakswmintro.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="rzaksbusinesscompare" />
|
||
<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>Your system as a business</title>
|
||
</head>
|
||
<body id="rzaksbusinesscompare"><a name="rzaksbusinesscompare"><!-- --></a>
|
||
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
<h1 class="topictitle1">Your system as a business</h1>
|
||
<div><p>To make grasping the overall concept of work management easier,
|
||
try comparing your system with a business.</p>
|
||
<p>A simple system can be compared to a small business, and a complex system
|
||
can be compared to a shopping mall. Assume there is a small store in the business
|
||
of building hand-crafted wood furniture. <em>Work enters</em>, such as orders
|
||
for small tables, chairs, and bookshelves. <em>Work is processed</em>, the carpenter
|
||
calls the customers to confirm the order, and they are consulted on design
|
||
points including style, size, and color. The carpenter designs each piece
|
||
of furniture, gathers the necessary materials, and then builds the furniture.
|
||
After the furniture is completed, it is delivered: <em>work leaves</em>.</p>
|
||
<p> Since a complex system is a combination of many simple systems, a comparable
|
||
example of a complex system is a shopping mall, many small and large businesses
|
||
in one area. Maybe the carpenter has a business in the Northwest corner of
|
||
the mall and a baker has a business along the East strip. The baker and the
|
||
carpenter have different input and different output, that is, their orders
|
||
and their products are very different. In addition, the time it takes each
|
||
business to process their work is quite different, and their users know and
|
||
understand that.</p>
|
||
<div class="section"><h4 class="sectiontitle">Work management terms</h4><p>A complex system (shopping
|
||
mall) is a compilation of many simple systems (stores). These simple systems
|
||
are called <dfn class="term">subsystems</dfn>.</p>
|
||
<p>Any piece of work within the business
|
||
is considered a <dfn class="term">job.</dfn> An example of a piece of work might be a
|
||
customer letter, a telephone call, an order, or nightly cleanup. The same
|
||
can be said about the IBM<sup>®</sup> iSeries™ system. On the system, each job has a unique
|
||
name. </p>
|
||
<p>A <dfn class="term">job description</dfn> describes how to handle the work
|
||
coming into the subsystem. Job descriptions contain pieces of information
|
||
such as user IDs, job queues, and routing data. Information in the job description
|
||
might compare to descriptions of jobs in a small business. </p>
|
||
<p><strong>What
|
||
does the business look like?</strong> Every store has blueprints or store plans.
|
||
These plans are really just descriptions, in varying detail, of the physical
|
||
makeup of the business. Maybe the business has a store with: 2 floors, 5 doors,
|
||
3 mailboxes, and 2 telephones. On the iSeries system, a <dfn class="term">subsystem description </dfn>contains
|
||
all the information about the subsystem. </p>
|
||
<p><strong>Where does the work come
|
||
from?</strong> For the carpenter, the work comes from customer calls, from references,
|
||
and from people that stop in. On the iSeries system, the work can come from
|
||
many places. Examples include job queues, workstations, communications, autostart
|
||
jobs, and prestart jobs. </p>
|
||
<p><strong>Where do they find the space?</strong> Within
|
||
the mall, each business (subsystem) has a certain amount of floor space. On
|
||
the iSeries system, <dfn class="term">memory
|
||
pools</dfn> allow you to control the main storage (or floor space) each subsystem
|
||
(business) gets to do its work. The more floor space a store (subsystem) has,
|
||
the more customers, or jobs, can fit in the store. </p>
|
||
<p><strong>How does the
|
||
work come in?</strong> Customers that cannot find the store they need may find
|
||
an information booth to help send them in the right direction. The same is
|
||
true on the iSeries system. <dfn class="term">Routing
|
||
entries</dfn> are similar to store directories or an information booth. After
|
||
the routing entry is found, it guides the job to its correct place. The routing
|
||
entry needs to be found first, however. That is done through <dfn class="term">routing
|
||
data</dfn>. Routing data is what the job uses to find the right routing entry. </p>
|
||
<p><strong>How
|
||
is the work treated?</strong> A carpenter needs to place a priority on each job.
|
||
The chair due at the end of the week should be done before the bookshelf due
|
||
at the end of the month. On the iSeries system, <dfn class="term">classes</dfn> provide
|
||
information about how the job is handled while in the subsystem. This information
|
||
includes priority while running, maximum storage, maximum CPU time, and time
|
||
slice. Each of these attributes contribute to how and when a job is processed. </p>
|
||
<p>Just
|
||
as there are rules that affect all the stores in the mall, there are rules
|
||
that affect all the subsystems on the iSeries system. An example of these rules
|
||
is a <dfn class="term">system value</dfn>. System values are pieces of information that
|
||
apply to the whole system. System values include information such as, date
|
||
and time, configuration information, signon information, system security and,
|
||
storage handling.</p>
|
||
<p> Customers in a mall each have information specific
|
||
to them. On the iSeries system,
|
||
the <dfn class="term">user profile</dfn> holds information specific to a particular user.
|
||
Similar to a customer’s credit card, a user profile gives that user specific
|
||
authorities and assigns the user attributes for that user's jobs.
|
||
These <dfn class="term">job attributes</dfn> provide information that includes, but is
|
||
not limited to, the job description, the output queue or printer device, the
|
||
message queue, the accounting code, and the scheduling priority.</p>
|
||
</div>
|
||
</div>
|
||
<div>
|
||
<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> |