114 lines
7.3 KiB
HTML
114 lines
7.3 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="concept" />
|
||
|
|
<meta name="DC.Title" content="Example: Connect a server to another server" />
|
||
|
|
<meta name="abstract" content="This example shows how to create Advanced Program-to-Program Communication (APPC) over token-ring connection from your server to another server." />
|
||
|
|
<meta name="description" content="This example shows how to create Advanced Program-to-Program Communication (APPC) over token-ring connection from your server to another server." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzajusnaconfigurationexamples.htm" />
|
||
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 1999, 2006" />
|
||
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 1999, 2006" />
|
||
|
|
<meta name="DC.Format" content="XHTML" />
|
||
|
|
<meta name="DC.Identifier" content="as400_to_as400_lan_example" />
|
||
|
|
<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>Example: Connect a server to another server</title>
|
||
|
|
</head>
|
||
|
|
<body id="as400_to_as400_lan_example"><a name="as400_to_as400_lan_example"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Example: Connect a server to another server</h1>
|
||
|
|
<div><p>This example shows how to create Advanced Program-to-Program Communication
|
||
|
|
(APPC) over token-ring connection from your server to another server.</p>
|
||
|
|
<p>The name of the local server is LOCAL, and the name of
|
||
|
|
the remote system is REMOTE.</p>
|
||
|
|
<div class="note"><span class="notetitle">Note:</span> Because all the examples use the same token-ring line description, this
|
||
|
|
example discusses only the controller and device descriptions.</div>
|
||
|
|
<p>Focus on these points in this example:</p>
|
||
|
|
<ul><li>The service access points (SAPs) in the controller descriptions. For more
|
||
|
|
information about SAPs, read <a href="rzajuhigherlayersoverlanprotocols.htm#higher_layers_over_lan_protocols">SNA
|
||
|
|
connections to LAN protocols</a>.</li>
|
||
|
|
<li>The adapter address used by a controller description must match the address
|
||
|
|
that is used in the line description on the remote device. This table shows
|
||
|
|
the adapter addresses that are used by the line and controller descriptions
|
||
|
|
on both systems.
|
||
|
|
<div class="tablenoborder"><a name="as400_to_as400_lan_example__local_remote_addresses"><!-- --></a><table cellpadding="4" cellspacing="0" summary="" id="as400_to_as400_lan_example__local_remote_addresses" class="singleborder" frame="border" border="1" rules="all"><caption>Table 1. Local and remote adapter addresses</caption><thead align="left"><tr><th align="center" valign="top" width="45.90643274853801%" id="d0e35"> </th>
|
||
|
|
<th align="center" valign="top" width="26.900584795321635%" id="d0e36">LOCAL</th>
|
||
|
|
<th align="center" valign="top" width="27.192982456140353%" id="d0e38">REMOTE</th>
|
||
|
|
</tr>
|
||
|
|
</thead>
|
||
|
|
<tbody><tr><td align="left" valign="top" width="45.90643274853801%" headers="d0e35 ">Adapter address in line description</td>
|
||
|
|
<td align="left" valign="top" width="26.900584795321635%" headers="d0e36 ">400003190001</td>
|
||
|
|
<td align="left" valign="top" width="27.192982456140353%" headers="d0e38 ">400003200001</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td align="left" valign="top" width="45.90643274853801%" headers="d0e35 ">Adapter address referred to by the controller
|
||
|
|
description</td>
|
||
|
|
<td align="left" valign="top" width="26.900584795321635%" headers="d0e36 ">400003200001</td>
|
||
|
|
<td align="left" valign="top" width="27.192982456140353%" headers="d0e38 ">400003190001</td>
|
||
|
|
</tr>
|
||
|
|
</tbody>
|
||
|
|
</table>
|
||
|
|
</div>
|
||
|
|
</li>
|
||
|
|
<li>The way a system identifies the other system to which it connects. Both
|
||
|
|
sides must use the same method. These are the methods: <ul><li>Only use the Remote exchange identifier parameter.</li>
|
||
|
|
<li>Use the Remote network identifier and the Remote control point name parameters.</li>
|
||
|
|
</ul>
|
||
|
|
In this example, each system uses the Remote network identifier and Remote
|
||
|
|
control point name (RMTCPNAME) parameters to indicate the system to which
|
||
|
|
it connects. <p>Note that within a system the remote network identifier must
|
||
|
|
be the same in the controller and device description. Because the example
|
||
|
|
uses the default value of *NETATR for the Remote network identifier parameter,
|
||
|
|
this parameter is not shown.</p>
|
||
|
|
<p>Get the value for the Remote control point
|
||
|
|
name parameter from the other system. To do this, use the Display Network
|
||
|
|
Attributes (DSPNETA) command on the other system and locate the Local control
|
||
|
|
point name field.</p>
|
||
|
|
</li>
|
||
|
|
</ul>
|
||
|
|
<p id="as400_to_as400_lan_example__tokenring2"><a name="as400_to_as400_lan_example__tokenring2"><!-- --></a><strong>TOKENRING2:</strong></p>
|
||
|
|
<p>This example uses this line description on the remote system.</p>
|
||
|
|
<pre>CRTLINTRN LIND(<strong>TOKENRING2</strong>) RSRCNAME(TRN_IOA) LINESPEED(16M)
|
||
|
|
MAXFRAME(16393) ADPTADR(400003200001) EXCHID(05600000)
|
||
|
|
SSAP((04 *MAXFRAME *CALC) (08 *MAXFRAME *CALC))
|
||
|
|
TEXT('Line description for 400003200001') </pre>
|
||
|
|
<p><strong>Controller descriptions:</strong></p>
|
||
|
|
<p>These examples show the controller descriptions that are used on the local
|
||
|
|
and remote systems.</p>
|
||
|
|
<pre>CRTCTLAPPC CTLD(LOCAL_CD) LINKTYPE(*LAN) SWTLINLST(<a href="rzajusnaconfigurationexamples.htm#sna_configuration_examples__tokenring1">TOKENRING1</a>)
|
||
|
|
RMTCPNAME(REMOTECP) ADPTADR(400003200001) DSAP(04)
|
||
|
|
SSAP(08) TEXT('Controller description on LOCAL')
|
||
|
|
|
||
|
|
CRTCTLAPPC CTLD(REMOTE_CD) LINKTYPE(*LAN) SWTLINLST(TOKENRING2)
|
||
|
|
RMTCPNAME(LOCALCP) ADPTADR(400003190001) DSAP(08)
|
||
|
|
SSAP(04) TEXT('Controller description on REMOTE')</pre>
|
||
|
|
<p><strong>Device descriptions:</strong></p>
|
||
|
|
<p>In the device descriptions, the Remote network identifier (RMTNETID) parameter
|
||
|
|
should match the local network-identifier of the remote system. You must use
|
||
|
|
the Display Network Attributes (DSPNETA) command on the remote system to view
|
||
|
|
the local network-identifier.</p>
|
||
|
|
<pre>CRTDEVAPPC DEVD(LOCAL_DD) RMTLOCNAME(REMOTE) LCLLOCNAME(LOCAL)
|
||
|
|
CTL(LOCAL_CD) MODE(BLANK)
|
||
|
|
TEXT('APPC device description describing system REMOTE')
|
||
|
|
|
||
|
|
CRTDEVAPPC DEVD(REMOTE_DD) RMTLOCNAME(LOCAL) LCLLOCNAME(REMOTE)
|
||
|
|
CTL(REMOTE_CD) MODE(BLANK)
|
||
|
|
TEXT('APPC device description describing system LOCAL')</pre>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzajusnaconfigurationexamples.htm" title="These examples describe the dependencies of a parameter or the required parameter values for various SNA network environments.">Examples: Configure SNA over token ring</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|