87 lines
5.2 KiB
HTML
87 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 xmlns="http://www.w3.org/1999/xhtml" lang="en-US" xml:lang="en-us">
|
|
<head>
|
|
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
|
|
<meta name="dc.language" scheme="rfc1766" 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. -->
|
|
<meta name="dc.date" scheme="iso8601" content="2005-09-06" />
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 1998, 2006" />
|
|
<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))' />
|
|
<title>Considerations for subsystem configuration for error recovery performance</title>
|
|
<link rel="stylesheet" type="text/css" href="ibmidwb.css" />
|
|
<link rel="stylesheet" type="text/css" href="ic.css" />
|
|
</head>
|
|
<body>
|
|
<a id="Top_Of_Page" name="Top_Of_Page"></a><!-- Java sync-link -->
|
|
<script language = "Javascript" src = "../rzahg/synch.js" type="text/javascript"></script>
|
|
|
|
|
|
<a name="rzajterr-consubinsts"></a>
|
|
<h4 id="rzajterr-consubinsts">Considerations for subsystem configuration for error recovery performance</h4>
|
|
<p>Each piece of work that runs on the iSeries™ system is called a job. Each job is
|
|
a single, identifiable sequence of processing actions that represents a single
|
|
use of the system. The basic types of jobs performed are interactive jobs,
|
|
batch jobs, spooling jobs, autostart jobs, and prestart jobs.</p>
|
|
<p>Jobs that run in subsystems do all work that is performed on the iSeries server. As
|
|
the number of users on the system increases, it becomes important for you
|
|
to consider how the communications and interactive subsystems should be configured.</p>
|
|
<p> The configuration of subsystems has little impact in normal data path
|
|
operations. However, multiple subsystems can provide multiple processes to
|
|
do cleanup and recovery when error conditions occur. This can result in improved
|
|
performance.</p>
|
|
<p>As the number of users on the system increases, you must consider the importance
|
|
of how subsystems are configured:</p>
|
|
<ul>
|
|
<li>Consider limiting the number of devices that are serviced by a single
|
|
subsystem. Between 200 and 300 devices for each subsystem are recommended.
|
|
Use the following recommendations to divide these users:
|
|
<ul>
|
|
<li>The number of users in any given subsystem</li>
|
|
<li>The connectivity used to access the system</li>
|
|
<li>The type of work the users do</li>
|
|
<li>The geographic location of the users</li></ul></li>
|
|
<li>Create additional communications and interactive subsystems to split the
|
|
work into multiple subsystems.</li>
|
|
<li>The work that is performed in the QCMN subsystem is for connecting and
|
|
disconnecting from the system. Error recovery considerations are important
|
|
in the configuration of the communications subsystem.</li>
|
|
<li>To prevent a subsystem from allocating a device, ensure that there are
|
|
no workstation or type entries for the devices that you do not want to be
|
|
allocated.</li>
|
|
<li>Only use the AT(*ENTER) option if you must allow jobs to transfer into
|
|
that subsystem.</li>
|
|
<li>For each subsystem you have defined, you need to identify which users
|
|
will run in which subsystems. Use the Add Work Station Entry (ADDWSE) command
|
|
and the Remove Work Station Entry (RMVWSE) command. You can set up workstation
|
|
entries that identify which devices that subsystem should allocate, as well
|
|
as which devices a subsystem should not allocate.</li></ul>
|
|
<a name="wq7"></a>
|
|
<div class="notetitle" id="wq7">Note:</div>
|
|
<div class="notebody">You can use the ADDWSE commands while the subsystem is active.
|
|
However, subsystems do not reallocate device locks dynamically. Eventually,
|
|
it might be necessary to end and restart the subsystems to have the device
|
|
locks allocated to the choosen subsystem.</div>
|
|
<p>To specify the devices a communications subsystem <span class="bold">should</span> allocate:</p>
|
|
<pre class="xmp">ADDCMNE SBSD(libname/sbsname) DEV(devname*) MODE(modename)</pre>
|
|
<p>To specify the devices a communications subsystem <span class="bold">should
|
|
not</span> allocate:</p>
|
|
<pre class="xmp">ADDCMNE SBSD(libname/sbsname) DEV(devname*) MODE(modename) MAXACT(0)</pre>
|
|
<a name="wq8"></a>
|
|
<div class="notetitle" id="wq8">Note:</div>
|
|
<div class="notebody">Database and file servers run only in QSERVER when running
|
|
over APPC. Do not attempt to allocate sessions running over the QSERVER mode
|
|
description. These servers can run over TCP/IP and only then can you run them
|
|
in subsystems other than QSERVER.</div>
|
|
<p>See the following <a href="rzajtrzajterrexm1.htm#rzajterr-exm1">example</a> for a way of configuring
|
|
your communications subsystem.</p>
|
|
<a id="Bot_Of_Page" name="Bot_Of_Page"></a>
|
|
</body>
|
|
</html>
|