59 lines
3.6 KiB
HTML
59 lines
3.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 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>Adjust WAN protocols for optimum iSeries server 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="rzajtper-wanprofacts"></a>
|
||
|
<h4 id="rzajtper-wanprofacts">Adjust WAN protocols for optimum iSeries server performance</h4>
|
||
|
<p>Wide area network (WAN) protocols affect the communications performance
|
||
|
on the iSeries™ server. Let us use X.25 for our example. For each X.25 communications
|
||
|
controller, the iSeries server has some processing limitations for the
|
||
|
line, the line speed, and the total number of virtual circuits that can be
|
||
|
used. Performance degradation can be reduced by observing these limitations.</p>
|
||
|
<p>To optimize the iSeries system performance for wide area networks, perform
|
||
|
these tasks:</p>
|
||
|
<ul>
|
||
|
<li>Reduce the total number of frames by using larger frames.</li>
|
||
|
<li>To take advantage of these large frame sizes, change the MAXFRAME parameter
|
||
|
on the line description (LIND) to reflect the maximum value. For X.25, increase
|
||
|
the DFTPKTSIZE and MAXFRAME parameters to their maximum value.</li>
|
||
|
<li>Configure a WAN line as full-duplex to provide you with a higher throughput
|
||
|
for applications that can take advantage of this mode. This can also provide
|
||
|
higher throughput for multiple users.</li>
|
||
|
<li>Increase frame relay to capacity.</li></ul>
|
||
|
<p>The data rate for a given protocol might increase as frame size increases.
|
||
|
Under these circumstances, the central processing unit (CPU) and the input/output
|
||
|
processor (IOP) do not do as much processing. Fewer and larger frames also
|
||
|
make more efficient use of the communications line (higher effective data
|
||
|
rate) because of fewer overhead bytes and line turn-arounds.</p>
|
||
|
<p>Frame relay has equivalent performance over RS449, X.21, and V.35 assuming
|
||
|
equal line speeds and conditions. Frame relay performance (CPU time) is similar
|
||
|
to or slightly better than Synchronous Data Link Control. For properly tuned
|
||
|
large transfer applications, the CPU and IOP have no problem using the line
|
||
|
speed to capacity.</p>
|
||
|
<p>For information about configuring iSeries system communications, see the <a href="../books/c4154010.pdf" target="_blank">Communications Configuration</a>
|
||
|
<img src="wbpdf.gif" alt="Link to PDF" /> book.</p>
|
||
|
<a id="Bot_Of_Page" name="Bot_Of_Page"></a>
|
||
|
</body>
|
||
|
</html>
|