69 lines
4.4 KiB
HTML
69 lines
4.4 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-10-03" />
|
||
|
|
<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>Select your APPC networking protocol</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="rzahjper-comselenvinsts"></a>
|
||
|
|
<h3 id="rzahjper-comselenvinsts">Select your APPC networking protocol</h3>
|
||
|
|
<p>When choosing the advanced program-to-program communications (APPC) networking
|
||
|
|
protocol for your business, you should understand some of the operational
|
||
|
|
characteristics for APPN and HPR. These operational characteristics may affect
|
||
|
|
communication performance on your system.</p>
|
||
|
|
<a name="wq4"></a>
|
||
|
|
<div class="notetitle" id="wq4">Note:</div>
|
||
|
|
<div class="notebody">While you can run
|
||
|
|
APPC without using APPN or HPR, it may be advantageous to use APPN or HPR
|
||
|
|
since they require less configuration than running pure APPC for your applications.</div>
|
||
|
|
<p>To help you choose your APPC networking protocol, consider the following:</p>
|
||
|
|
<ul>
|
||
|
|
<li>HPR provides a significant enhancement over APPN in terms of network availability
|
||
|
|
by establishing and maintaining end-to-end connections and the ability to
|
||
|
|
switch paths transparently. For HPR, segmentation and reassembly are accomplished
|
||
|
|
in the central processing unit (CPU). For APPN, the segmentation and reassembly
|
||
|
|
happen in the input/output processor (IOP). This HPR capability of being able
|
||
|
|
to transparently switch paths comes with additional central processing (CPU)
|
||
|
|
usage as compared to APPN.</li>
|
||
|
|
<li><img src="delta.gif" alt="Start of change" />Enterprise Extender is a networking architecture that allows
|
||
|
|
Systems Network Architecture (SNA) applications to run over Internet Protocol
|
||
|
|
(IP) networks using High Performance Routing (HPR). This is the preferred
|
||
|
|
way to run SNA applications over IP networks with communications input/output
|
||
|
|
adapters (IOAs), such as Gigabit Ethernet, since these IOAs do not require
|
||
|
|
an input/output processor (IOP). Communications adapters that do not use an
|
||
|
|
IOP do not support SNA, therefore, Enterprise Extender is required to run
|
||
|
|
SNA over these adapters. IBM® recommends that Enterprise Extender be used in place
|
||
|
|
of AnyNet®. For more information, see <a href="../rzajt/rzajtanytoee.htm">Migration from AnyNet to Enterprise Extender</a>.<img src="deltaend.gif" alt="End of change" /></li>
|
||
|
|
<li>The choice of which protocol to use really comes down to deciding whether
|
||
|
|
the high availability features of HPR are desirable in your environment. When
|
||
|
|
determining whether to use APPN or HPR, you should consider the following:
|
||
|
|
<ul>
|
||
|
|
<li>The high-availability feature of HPR</li>
|
||
|
|
<li>The feasibility of higher CPU usage for your environment with HPR</li>
|
||
|
|
<li><img src="delta.gif" alt="Start of change" />The requirement to use HPR with Enterprise Extender<img src="deltaend.gif" alt="End of change" /></li></ul></li></ul>
|
||
|
|
<p>You can control the selection of APPN or HPR easily by manipulating the
|
||
|
|
network attributes. It is just as simple to change from HPR to APPN as it
|
||
|
|
is to change from APPN to HPR. The best way to determine the affect of using
|
||
|
|
HPR and APPN in your environment would be to perform some of your own benchmarks.</p>
|
||
|
|
<a id="Bot_Of_Page" name="Bot_Of_Page"></a>
|
||
|
|
</body>
|
||
|
|
</html>
|