101 lines
5.7 KiB
HTML
101 lines
5.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="task" />
|
|||
|
<meta name="DC.Title" content="Configure SNA for virtual OptiConnect" />
|
|||
|
<meta name="abstract" content="In IBM networks, Systems Network Architecture (SNA) is the layered logical structure, formats, protocols, and operational sequences that are used for transmitting information units through networks. SNA also controls the configuration and operation of networks." />
|
|||
|
<meta name="description" content="In IBM networks, Systems Network Architecture (SNA) is the layered logical structure, formats, protocols, and operational sequences that are used for transmitting information units through networks. SNA also controls the configuration and operation of networks." />
|
|||
|
<meta name="DC.Relation" scheme="URI" content="rzaitvirtualconn.htm" />
|
|||
|
<meta name="DC.Relation" scheme="URI" content="rzaitvirtualconn.htm" />
|
|||
|
<meta name="copyright" content="(C) Copyright IBM Corporation 2004, 2006" />
|
|||
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 2004, 2006" />
|
|||
|
<meta name="DC.Format" content="XHTML" />
|
|||
|
<meta name="DC.Identifier" content="rzaitsna" />
|
|||
|
<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>Configure SNA for virtual OptiConnect</title>
|
|||
|
</head>
|
|||
|
<body id="rzaitsna"><a name="rzaitsna"><!-- --></a>
|
|||
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|||
|
<h1 class="topictitle1">Configure SNA for virtual OptiConnect</h1>
|
|||
|
<div><p>In IBM<sup>®</sup> networks,
|
|||
|
Systems Network Architecture (SNA) is the layered logical structure, formats,
|
|||
|
protocols, and operational sequences that are used for transmitting information
|
|||
|
units through networks. SNA also controls the configuration and operation
|
|||
|
of networks.</p>
|
|||
|
<div class="section"><p>You can use SNA communications in a partitioned environment. SNA
|
|||
|
communication is limited to APPC using virtual OptiConnect. You can only communicate
|
|||
|
directly between two servers. In order to communicate with partitions that
|
|||
|
are not part of your server, you will have to access the server that has access
|
|||
|
to the network.</p>
|
|||
|
<p>To establish an APPC connection from a primary partition
|
|||
|
to a secondary partition, follow these steps:</p>
|
|||
|
</div>
|
|||
|
<ol><li class="stepexpand"><span>At a command line, enter the command CRTCTLAPPC and press <span class="uicontrol">Enter</span>.</span></li>
|
|||
|
<li class="stepexpand"><span>From the Create Controller Description (APPC) display, provide
|
|||
|
the following information: </span> <p>Controller description (Name)<br />
|
|||
|
Link type (*OPC)<br />
|
|||
|
Remote System Name (System name)<br />
|
|||
|
Data link role (*pri) <br />
|
|||
|
Text description</p>
|
|||
|
</li>
|
|||
|
<li class="stepexpand"><span>At the command line, enter the command CRTDEVAPPC and press <span class="uicontrol">Enter</span>.</span></li>
|
|||
|
<li class="stepexpand"><span>From the Create Device Description (APPC) display, provide the
|
|||
|
following information: </span> <p>Device description (Name)<br />
|
|||
|
Option (*BASIC)<br />
|
|||
|
Category of device (*APPC) <br />
|
|||
|
Remote location (Provide the same system name found in the <br />
|
|||
|
Display Network Attributes (DSPNETA) display.)<br />
|
|||
|
Online at IPL (*YES)<br />
|
|||
|
Local location (Name)<br />
|
|||
|
Remote network identifier (*None)<br />
|
|||
|
Attached controller (Name)<br />
|
|||
|
APPN-capable (*NO)</p>
|
|||
|
</li>
|
|||
|
</ol>
|
|||
|
<div class="section"><p>To establish an APPC connection from a secondary partition, following
|
|||
|
these steps:</p>
|
|||
|
<ol><li>At a command line, enter the command CRTCTLAPPC and press <span class="uicontrol">Enter</span>.</li>
|
|||
|
<li>From the Create Controller Description (APPC) display, provide the following
|
|||
|
information: <p>Controller description (Name)<br />
|
|||
|
Link type (*OPC)<br />
|
|||
|
Remote System Name (System name) <br />
|
|||
|
Data link role (*SEC) <br />
|
|||
|
Text description</p>
|
|||
|
</li>
|
|||
|
<li>At the command line, enter the command CRTDEVAPPC and press <span class="uicontrol">Enter</span>.</li>
|
|||
|
<li>From the Create Device Description (APPC) display, provide the following
|
|||
|
information: <p>Device description (Name)<br />
|
|||
|
Option (*BASIC)<br />
|
|||
|
Category of device (*APPC)<br />
|
|||
|
Remote location (Name)<br />
|
|||
|
Online at IPL (*YES)<br />
|
|||
|
Local location (Name) <br />
|
|||
|
Remote network identifier (*None)<br />
|
|||
|
Attached controller (Name)<br />
|
|||
|
APPN-capable (*NO)</p>
|
|||
|
</li>
|
|||
|
</ol>
|
|||
|
</div>
|
|||
|
</div>
|
|||
|
<div>
|
|||
|
<div class="familylinks">
|
|||
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaitvirtualconn.htm" title="Virtual OptiConnect allows one partition to communicate with another partition if both partitions have virtual OptiConnect enabled.">Virtual OptiConnect</a></div>
|
|||
|
</div>
|
|||
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
|||
|
<div><a href="rzaitvirtualconn.htm" title="Virtual OptiConnect allows one partition to communicate with another partition if both partitions have virtual OptiConnect enabled.">Virtual OptiConnect</a></div>
|
|||
|
</div>
|
|||
|
</div>
|
|||
|
</body>
|
|||
|
</html>
|