145 lines
8.9 KiB
HTML
145 lines
8.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-17" />
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 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>Configure extended function path routing</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="ctld"></a>
|
|
<h2 id="ctld">Configure extended function path routing</h2>
|
|
<p>Extended function path OptiConnect requires the configuration of an APPC
|
|
device and controller. The controller description will have a type of *OPC,
|
|
indicating to the device driver layer to use the bus. However, you cannot
|
|
bypass some of the communication layers, as with the Fastpath method. This
|
|
method is necessary for certain functions like two-phase commit, and some Lotus® Domino® Applications (LS:DO) that use LS:DO to access remote data. This
|
|
is known as Extended Function Path OptiConnect.</p>
|
|
<p>To route data requests through OptiConnect without using the special device
|
|
keyword, you create OptiConnect controllers and devices of type *OPC. The
|
|
*OPC controller needs to be link type of *OPC. The remote system name must
|
|
be the name of the target system.</p>
|
|
<p>Use the following commands to configure the *OPC controller: </p>
|
|
<ol type="1">
|
|
<li id="ej1">
|
|
<a name="ej1"></a>Create the controller description.
|
|
<pre class="xmp">CRTCTLAPPC CTLD(name) LINKTYPE(*OPC) RMTSYSNAME(sysname)
|
|
ROLE(*PRI or *SEC) DSAP(##) </pre> You must create a pair of *OPC controllers
|
|
(one on each of the two systems that uses OptiConnect to communicate). The
|
|
Data Link Role of one system must be *PRI (primary), and the other must be
|
|
*SEC (secondary). Setting the destination service access point (DSAP) value
|
|
will set both the source service access point (SSAP), and DSAP parameters.
|
|
The DSAP value must be valid and identical for both controllers on both systems
|
|
in the pair. Valid values are 04, 08, 0C, 10, 14, ...78, 7C.
|
|
<p>The following
|
|
is an example of creating an *OPC controller on two systems: SYSTEMA and SYSTEMB.
|
|
To create a controller on SYSTEMA to connect to SYSTEMB, enter the Create
|
|
Controller Description (CRTCTLAPPC) command. The joblog now shows: </p>
|
|
<pre class="xmp"> > CRTCTLAPPC CTLD(SYSBCTL) LINKTYPE(*OPC) RMTSYSNAME(SYSTEMB)
|
|
ROLE(*PRI) DSAP(44)
|
|
Description for controller SYSBCTL created.</pre></li>
|
|
<li id="ej2">
|
|
<a name="ej2"></a>Create a device description for each controller on each system.
|
|
<pre class="xmp">CRTDEVAPPC DEVD(SYSBDEV) RMTLOCNAME(SYSB) ONLINE(*NO) LCLLOCNAME(SYSA)
|
|
CTL(SYSBCTL) APPN(*NO) </pre>
|
|
<p>The *OPC controller will only accept devices
|
|
that are created with APPN(*NO). The RMTLOCNAME and LCLLOCNAME need to be
|
|
mirror images of the RMTLOCNAME and LCLLOCNAME on the other system in the
|
|
'pair.' Parameter ONLINE at IPL should be *NO since you cannot vary on OptiConnect
|
|
controllers and attached devices until the QSOC subsystem has started.</p>
|
|
<p>The following are examples for creating an *OPC device description to attach
|
|
to the controller. To create a device description on SYSTEMA to attach to
|
|
controller SYSBCTL, enter the Create Device Description (CRTDEVAPPC) command.</p>
|
|
<p>The joblog now shows: </p>
|
|
<pre class="xmp"> > CRTDEVAPPC DEVD(SYSBDEV) RMTLOCNAME(SYSB) ONLINE(*NO)
|
|
LCLLOCNAME(SYSA) CTL(SYSBCTL) APPN(*NO)
|
|
Description for device SYSBDEV created.</pre></li>
|
|
<li id="ej3">
|
|
<a name="ej3"></a>On the other system in the 'pair,' create a controller and device
|
|
description that will point to the previously created descriptions. On SYSTEMB
|
|
enter the CRTCTLAPPC command to connect to SYSTEMA.
|
|
<p>The joblog now shows:
|
|
</p>
|
|
<pre class="xmp"> > CRTCTLAPPC CTLD(SYSACTL) LINKTYPE(*OPC)
|
|
RMTSYSNAME(SYSTEMA) ROLE(*SEC) DSAP(44)
|
|
Description for controller SYSACTL created.</pre></li>
|
|
<li id="ej4">
|
|
<a name="ej4"></a>Create a device description on SYSTEMB to attach to controller
|
|
SYSACTL. Enter the CRTDEVAPPC command.
|
|
<p>The joblog now shows: </p>
|
|
<pre class="xmp"> > CRTDEVAPPC DEVD(SYSADEV) RMTLOCNAME(SYSA) ONLINE(*NO)
|
|
LCLLOCNAME(SYSB) CTL(SYSACTL) APPN(*NO)
|
|
Description for device SYSADEV created.</pre></li>
|
|
<li>Repeat steps <a href="rzau3ctld.htm#ej1">1</a> and <a href="rzau3ctld.htm#ej2">2</a> for
|
|
all the system pairs in the OptiConnect network.</li>
|
|
<li>Vary on all *OPC controllers and devices to enable requests over OptiConnect.
|
|
<p>When the first of a pair of *OPC controllers is varied on, the status of the
|
|
controller changes to <tt class="xph">ACTIVE/CNN PENDING</tt> or <tt class="xph">VARYON/CNN PENDING</tt>. That is, if the device is not varied on. This indicates that the OptiConnect
|
|
path is not yet completely established. After the second of the *OPC pair
|
|
is varied on, both controllers change to <tt class="xph">ACTIVE </tt> status, and the
|
|
OptiConnect connection is available for data transfer.</p>
|
|
<a name="wq16"></a>
|
|
<div class="notetitle" id="wq16">Note:</div>
|
|
<div class="notebody">You must start the QSOC subsystem on both systems prior to varying on the
|
|
*OPC controller and its associated devices. If the QSOC subsystem is ended
|
|
on any system, the controllers on that system, and all connected systems,
|
|
change to a status of <tt class="xph">ACTIVE/CNN PENDING</tt> or <tt class="xph">VARYON/CNN PENDING</tt>. After the QSOC subsystem has restarted, there cannot be any activity
|
|
through these controllers until they are varied off, and then back on.</div>
|
|
<p>The following are examples to vary on controllers and devices.
|
|
Use the VRYCFG command on SYSTEMA to vary on controller SYSBCTL.</p>
|
|
<p>The
|
|
joblog now shows: </p>
|
|
<pre class="xmp"> > VRYCFG CFGOBJ(SYSBCTL) CFGTYPE(*CTL) STATUS(*ON)
|
|
Vary on completed for controller SYSBCTL.
|
|
Vary on completed for device SYSBDEV.</pre>
|
|
<p>Use the VRYCFG command
|
|
on SYSTEMB to vary on controller SYSACTL.</p>
|
|
<p>The joblog now shows: </p>
|
|
<pre class="xmp"> > VRYCFG CFGOBJ(SYSACTL) CFGTYPE(*CTL) STATUS(*ON)
|
|
Vary on completed for controller SYSACTL.
|
|
Vary on completed for device SYSADEV.</pre></li>
|
|
<li>Setup DDM files:
|
|
<p>Use the same locations for the Remote and Local location
|
|
parameters that were previously specified in the APPC device description.
|
|
Use *LOC for the device description parameter. Remote and Local Locations
|
|
that are defined in the devices attached to the *OPC controllers can also
|
|
be used in Structured Query Language (SQL) relational database directories.
|
|
For more information, see <a href="rzau3sqlrte.htm#sqlrte">SQL over OptiConnect</a>.</p></li></ol>
|
|
<p>Although varying on the *OPC controllers and devices enables traffic over
|
|
OptiConnect, varying off these devices and controllers does not necessarily
|
|
block that traffic. To make certain that OptiConnect activity is stopped,
|
|
use the vary option of the WRKOPCACT command, or end the QSOC subsystem.</p>
|
|
<p>The *OPC controllers can be used to provide APPC communication capability
|
|
across the OptiConnect bus. An application program using the ICF file interface,
|
|
the CPI communication call interface, or the CICS® file interface can communicate with an
|
|
application running on a remote system using OptiConnect. It is not restricted
|
|
to previous OptiConnect applications such as DDM and SQL.</p>
|
|
<p>The default QYCTSOC APPC device description has *PUBLIC authority *CHANGE
|
|
so any user can use OptiConnect. To keep the public from using OptiConnect,
|
|
issue the command Revoke Object Authority (RVKOBJAUT). Then, grant access
|
|
to the *DEVD for specific users with the Grant Object Authority (GRTOBJAUT)
|
|
command. </p>
|
|
<a name="wq17"></a>
|
|
<div class="notetitle" id="wq17">Note:</div>
|
|
<div class="notebody">The APPC device description does not describe a device,
|
|
but is used to control authority and access to the OptiConnect path.</div>
|
|
<a id="Bot_Of_Page" name="Bot_Of_Page"></a>
|
|
</body>
|
|
</html>
|