ibm-information-center/dist/eclipse/plugins/i5OS.ic.rzahj_5.4.0.1/rzahjnetattpi.htm

120 lines
6.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-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>Change network attributes</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="rzahjnetatt-pi"></a>
<h4 id="rzahjnetatt-pi">Change network attributes</h4>
<p>Network attributes describe the local system name, the default local location
name, the default control point name, the local network identifier, and the
network node type. If the machine is an end-node, the attributes also contain
the names of the network servers that are used by this iSeries&trade; system. Network
attributes also determine whether the system uses HPR, or whether you want
to use virtual controllers for APPN.</p>
<p><span class="bold">To change the network attributes, do the following</span>:</p>
<ol type="1">
<li>Vary off all APPC and host controllers. The easiest way to do this is
to use:
<pre class="xmp">VRYCFG CFGOBJ(*APPN) CFGTYPE(*CTL)
STATUS(*OFF) RANGE(*NET)</pre>
<a name="wq11"></a>
<div class="notetitle" id="wq11">Note:</div>
<div class="notebody">When using automatic
creation of controllers on LANs and you vary off the controllers, you have
approximately 2 minutes before the iSeries automatically varies on the controllers
again. If you have many configuration objects, temporarily turn off APPN auto-creation
on the LAN line by using the command CHGLINxxx AUTOCRTCTL(*NO), where xxx
is TRN, ETH, DDI, or WLS. When you have changed the necessary network attribute,
use the command CHGLINxxx AUTOCRTCTL(*YES) to resume normal APPN function.</div></li>
<li>Type the Change Network Attributes (CHGNETA) command on any iSeries command line
and press F4.</li>
<li>Use the online help information to complete the parameter values.</li>
<li>Press the Enter key. The network attributes are changed.</li>
<li>Vary on all the controllers that were varied off in the first step. Use:
<pre class="xmp">VRYCFG CFGOBJ(*PRVCFGTYPE) CFGTYPE(*CTL)
STATUS(*ON) RANGE(*NET)
</pre></li></ol>
<a name="wq12"></a>
<div class="notetitle" id="wq12">Note:</div>
<div class="notebody">The VRYCFG of *APPN will find <span class="bold">all</span> APPN
controllers and devices on the system and will try to vary them off. The VRYCFG
with *PRVCFGTYPE will then try to vary them <span class="bold">all</span> on.</div>
<p><span class="bold">Configuring APPN virtual controllers</span></p>
<p>On the iSeries, local applications that need to establish LU 6.2 sessions to
other locations in the APPN network require an APPC device description that
specifies APPN(*YES). For simplicity, these devices are referred to as APPN
devices. Multiple device descriptions can be created and used simultaneously
to communicate between the same local location and the remote location pair.
After a session is established, the controller description continues to use
the same APPN device description for the life of that session.</p>
<p><span class="bold">To configure virtual controllers, do the following:</span></p>
<ul>
<li>Set the ALWVRTAPPN network attribute to (*YES)</li></ul>
<p>After this is done, existing APPN device descriptions (attached to a real
controller description) will no longer be used.</p>
<p><span class="bold">If you do not want to use virtual APPN support:</span></p>
<ol type="1">
<li>Vary off the attached controller</li>
<li>Change the ALWVRTAPPN network attribute</li>
<li>Vary the controller back on</li></ol><p class="indatacontent">The APPN device can now be varied on.</p>
<a name="wq14"></a>
<div class="notetitle" id="wq14">Note:</div>
<div class="notebody">This does not affect
HPR since it always uses virtual APPN support.</div>
<p><span class="bold">If you are using the HPR tower option (RTP):</span></p>
<ol type="1">
<li>Vary off all APPN controllers. Use:
<pre class="xmp">VRYCFG CFGOBJ(*APPN) CFGTYPE(*CTL)
STATUS(*OFF) RANGE(*NET)</pre></li>
<li>Set the Allow HPR transport tower support (ALWHPRTWR) parameter to (*YES)</li>
<li>Vary on all your APPN controllers. Use:
<pre class="xmp">VRYCFG CFGOBJ(*PRVCFGTYPE) CFGTYPE(*CTL)
STATUS(*ON) RANGE(*NET)
</pre></li></ol>
<p><span class="bold">Configuring APPN using Branch Extender</span></p>
<p>To use Branch Extender, see the page <a href="rzahjrzahjbranchx.htm#rzahjbranchx">Configuring
Branch Extender support.</a></p>
<p>For more information about Branch Extender, see the page <a href="rzahjpernetdesinsts.htm#rzahjper-netdesinsts">Designing an APPN and HPR network to optimize communications performance</a>.</p>
<p><span class="bold">Considerations for system names</span></p>
<p>Use caution when you use names with the special characters # (X'7B'), $
('5B'), and @ ('7C'). These special characters might not be on the keyboard
of the remote system. These special characters are not supported for APPC
over TCP/IP (network IDs and location names only). The use of these symbols
should be limited to migration of the operating system. Do not use these characters
for newly created names.</p>
<p>If you are using a national language keyboard that does not have the #,
$, or @ symbols, see the appendix on national language keyboard types and
the appendix on code pages in the <a href="../nls/rbagsnatlangkeybrdtype.htm"> national language
keyboard types</a> topic in the Information Center.</p>
<p>The names that may be exchanged with remote systems include the following:</p>
<ul>
<li>Network IDs</li>
<li>Location names</li>
<li>Mode names</li>
<li>Class-of-service names</li>
<li>Control-point names</li>
<li>Connection network names</li></ul>
<a id="Bot_Of_Page" name="Bot_Of_Page"></a>
</body>
</html>