57 lines
3.7 KiB
HTML
57 lines
3.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="reference" />
|
||
|
|
<meta name="DC.Title" content="Performance degradation on local console" />
|
||
|
|
<meta name="abstract" content="The most likely reason for performance degradation is that the communication port is not running a buffered UART (Universal Asynchronous Receive/Transmit serial port chip)." />
|
||
|
|
<meta name="description" content="The most likely reason for performance degradation is that the communication port is not running a buffered UART (Universal Asynchronous Receive/Transmit serial port chip)." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzajrtroublelocalconnection.htm" />
|
||
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 2000, 2006" />
|
||
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 2000, 2006" />
|
||
|
|
<meta name="DC.Format" content="XHTML" />
|
||
|
|
<meta name="DC.Identifier" content="troubleperformance" />
|
||
|
|
<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>Performance degradation on local console</title>
|
||
|
|
</head>
|
||
|
|
<body id="troubleperformance"><a name="troubleperformance"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Performance degradation on local console</h1>
|
||
|
|
<div><p>The most likely reason for performance degradation is that the
|
||
|
|
communication port is not running a buffered UART (Universal Asynchronous
|
||
|
|
Receive/Transmit serial port chip).</p>
|
||
|
|
<div class="section"><p>Go into the <span class="uicontrol">Advanced</span> settings
|
||
|
|
for the serial port and verify the check mark is checked to use a buffered
|
||
|
|
UART. Make sure the Receive Buffer setting is not set to the right-most setting.</p>
|
||
|
|
</div>
|
||
|
|
<div class="section"><p>If that does not help and you suspect that there is a possibility
|
||
|
|
that the PC may truly not have the buffered UART, IBM<sup>®</sup> recommends that you slow the connection
|
||
|
|
down between the PC and server. Depending on the operating system, you may
|
||
|
|
have to change the registry, the DUN object, or the phone book entry, or all
|
||
|
|
three.</p>
|
||
|
|
</div>
|
||
|
|
<div class="section"><p>The problem when the UART is not buffered is that the high speed
|
||
|
|
inputs data to the UART faster than it can handle, which causes a missed packet
|
||
|
|
of data resulting in a 30-second retry. This can occur randomly, but will
|
||
|
|
be persistent. The slower speed reduces the exposure to an overrun of data
|
||
|
|
and therefore no more 30-second retries.</p>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzajrtroublelocalconnection.htm" title="When setting up your local console you may encounter problems connecting. Failure to connect is defined as problems resulting in the status not going to Connected and the emulator did not start.">Local console connection problems</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|