79 lines
4.9 KiB
HTML
79 lines
4.9 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>Communications performance considerations for interactive jobs</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="rzajtper-cominterjobsin"></a>
|
||
|
|
<h4 id="rzajtper-cominterjobsin">Communications performance considerations for interactive jobs</h4>
|
||
|
|
<p>An interactive job is one that uses a keyboard and character-type display.
|
||
|
|
If a job needs the user to type on the keyboard and display character results,
|
||
|
|
that job is probably considered interactive. Interactive in this sense means
|
||
|
|
that the job and the user depend on each other to get the work done.</p>
|
||
|
|
<p>To optimize communications performance for interactive jobs, consider the
|
||
|
|
following:</p>
|
||
|
|
<ul>
|
||
|
|
<li>Attach workstations through communications. This requires more CPU overhead
|
||
|
|
than 5250 local workstations.</li>
|
||
|
|
<li>Use a twinaxial controller to provide better performance than an American
|
||
|
|
National Standard Code for Information Interchange (ASCII) controller.</li>
|
||
|
|
<li>Keep the line utilization below 30 percent for best performance when interactive
|
||
|
|
users are attached. This maintains predictable and consistent response times.
|
||
|
|
Exceeding 50 to 60 percent line utilization will typically cause unacceptable
|
||
|
|
response times.</li></ul>
|
||
|
|
<p>If your system has interactive users who are connected many different ways,
|
||
|
|
you should consider configuring your interactive subsystems to separate the
|
||
|
|
users. Local workstation, remote workstations, 5250 display station pass-through,
|
||
|
|
or Telnet are some examples of these types of connections that should be separated.
|
||
|
|
When you configure interactive subsystems, identify how you want the interactive
|
||
|
|
users to be separated and create the appropriate subsystem descriptions.</p>
|
||
|
|
<p>During error recovery, when many users risk losing their sessions at one
|
||
|
|
time, an interactive subsystem can be very busy performing device recovery.
|
||
|
|
This device recovery can adversely affect the work of other users in the subsystem
|
||
|
|
who would otherwise be unaffected by the failure. Therefore, you might need
|
||
|
|
to change how the interactive subsystems are configured. However, multiple
|
||
|
|
subsystems can provide multiple processes to do cleanup and recovery when
|
||
|
|
error conditions occur. This can result in improved performance.</p>
|
||
|
|
<p>The example below shows how to configure an interactive subsystem to allocate
|
||
|
|
devices that begin with devname* and present a signon display on those display
|
||
|
|
devices: </p>
|
||
|
|
<pre class="xmp">ADDWSE SBSD(libname/sbsname) WRKSTNDEV(devname*) AT(*SIGNON)
|
||
|
|
</pre>
|
||
|
|
<p>Use the following example to configure an interactive subsystem so that
|
||
|
|
the device name devname* is not allocated and a signon display does not appear.</p>
|
||
|
|
<pre class="xmp">ADDWSE SBSD(libname/sbsname) WRKSTNDEV(devname*) AT(*ENTER)
|
||
|
|
</pre>
|
||
|
|
<p>Adding workstation entries with AT(*ENTER) allows you to use the Transfer
|
||
|
|
Job (TFRJOB) function into that subsystem. If the TFRJOB function is not required
|
||
|
|
or necessary, there is no need to add the workstation entries with AT(*ENTER).</p>
|
||
|
|
<p>To specify the devices an interactive subsystem<span class="bold"> should</span> allocate when the subsystem is started:</p>
|
||
|
|
<pre class="xmp">ADDWSE SBSD(libname/sbsname) WRKSTN(devname*) AT(*SIGNON)</pre>
|
||
|
|
<p>To specify the devices an interactive subsystem <span class="bold">should
|
||
|
|
not</span> allocate when the subsystem is started:</p>
|
||
|
|
<pre class="xmp">ADDWSE SBSD(libname/sbsname) WRKSTN(devname*) AT(*ENTER)</pre>
|
||
|
|
<ul>
|
||
|
|
<li>See the following <a href="rzajtrzajterrexm2.htm#rzajterr-exm2">example</a> for a way of
|
||
|
|
configuring your interactive subsystem.</li></ul>
|
||
|
|
<a id="Bot_Of_Page" name="Bot_Of_Page"></a>
|
||
|
|
</body>
|
||
|
|
</html>
|