74 lines
4.6 KiB
HTML
74 lines
4.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="Why consider multiple subsystems" />
|
|
<meta name="abstract" content="As the number of users on the system increases, a single subsystem for a set of work is often insufficient. By dividing your users into multiple subsystems you gain several advantages." />
|
|
<meta name="description" content="As the number of users on the system increases, a single subsystem for a set of work is often insufficient. By dividing your users into multiple subsystems you gain several advantages." />
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksaboutsbs.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="../experience/work1abstract.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="rzakssbsmultiple" />
|
|
<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>Why consider multiple subsystems</title>
|
|
</head>
|
|
<body id="rzakssbsmultiple"><a name="rzakssbsmultiple"><!-- --></a>
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|
<h1 class="topictitle1">Why consider multiple subsystems</h1>
|
|
<div><p>As the number of users on the system increases, a single subsystem
|
|
for a set of work is often insufficient. By dividing your users into multiple
|
|
subsystems you gain several advantages.</p>
|
|
<dl><dt class="dlterm">Improved manageability of work</dt>
|
|
<dd>You get better control over what work is running in each subsystem. For
|
|
example, for server jobs, you might want to isolate all of the database server
|
|
jobs to one subsystem, the remote command server jobs to a different subsystem,
|
|
the DDM server jobs to yet a different subsystem and so on. Additionally,
|
|
by using multiple subsystems you can isolate groups of jobs with their own
|
|
memory pools. In this way, one group does not adversely impact other jobs. </dd>
|
|
</dl>
|
|
<dl><dt class="dlterm">Reduced downtime impact for users</dt>
|
|
<dd>For example, if every Friday afternoon you must bring the system to the
|
|
restricted state for backup purposes, you can gradually take users offline
|
|
by ending one subsystem at a time.</dd>
|
|
</dl>
|
|
<dl><dt class="dlterm">Improved scalability and availability</dt>
|
|
<dd>By having a single subsystem do work for fewer users, the subsystem is
|
|
less busy and can be more responsive to the work requests it handles.</dd>
|
|
</dl>
|
|
<dl><dt class="dlterm">Improved error tolerance in interactive subsystems</dt>
|
|
<dd>By spreading the work across multiple subsystems, should a network failure
|
|
occur, multiple subsystems can manage the device recovery processing.</dd>
|
|
</dl>
|
|
<dl><dt class="dlterm">Improved interactive subsystem startup time</dt>
|
|
<dd>You can keep the subsystem startup times shorter by subdividing the work
|
|
across multiple subsystems.</dd>
|
|
</dl>
|
|
<dl><dt class="dlterm">Additional options for performance tuning</dt>
|
|
<dd>By using multiple subsystems you can set up the subsystems with a small
|
|
number of routing entries.</dd>
|
|
</dl>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaksaboutsbs.htm" title="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.">Subsystems</a></div>
|
|
</div>
|
|
<div class="relinfo"><strong>Related information</strong><br />
|
|
<div><a href="../experience/work1abstract.htm">Subsystem Configuration experience report</a></div>
|
|
</div>
|
|
</div>
|
|
</body>
|
|
</html> |