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

67 lines
3.5 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>Automatic creation and vary on of the controller description</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="rzahjvary-on"></a>
<h4 id="rzahjvary-on">Automatic creation and vary on of the controller description</h4>
<p>When APPN support determines that it needs a controller description automatically
varied on, it determines if there are any existing controller descriptions
that follow the naming convention for automatically created APPC controllers.</p>
<p>Naming convention for controller descriptions:</p>
<ul>
<li>The first controller description created has the same name as the CP name
of the adjacent system</li>
<li>Additional controller descriptions created use the following conventions:</li></ul>
<dl>
<dt class="bold">CPNAMExx</dt>
<dd>Where CPNAME is the adjacent system's control-point name and xx is some
value from 00-FF.
</dd>
</dl>
<p>If the adjacent system does not send a control-point name, then the local
system creates a name that is based on the adjacent system's EXCHID value.
The format of the name is: </p>
<dl>
<dt class="bold">CIIIIIxx</dt>
<dd>Where C is a constant value, IIIII is the exchange identifier (that
is not including the three-digit block number), and xx is some value from
'00-FF'.
</dd>
</dl>
<p>For an existing controller description to be considered a possible candidate
for being automatically varied on, it must: </p>
<ul>
<li>Satisfy the naming convention</li>
<li>Be an APPC controller description</li>
<li>Be in a varied off status</li>
<li>Have RMTCPNAME and RMTNETID parameters that match the incoming XID parameter</li>
<li>Have LINKTYPE parameter specified as *LAN.</li></ul><p class="indatacontent"> If no controllers are found that meet these initial requirements for
automatic vary on, then the system creates a new controller. The name of this
controller will be the first available name that follows the naming convention
for this remote control-point name, and the controller description will indicate
that the controller owner is the system (CTLOWN(*SYS)).</p>
<a id="Bot_Of_Page" name="Bot_Of_Page"></a>
</body>
</html>