84 lines
4.9 KiB
HTML
84 lines
4.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>SQL over OptiConnect</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="sqlrte"></a>
|
||
|
|
<h3 id="sqlrte">SQL over OptiConnect</h3>
|
||
|
|
<p>You can route Static and Dynamic Structured Query Language (SQL) over OptiConnect
|
||
|
|
through the use of Distributed Relational
|
||
|
|
Database Architecture™ (DRDA®). This can be done using either the
|
||
|
|
Fastpath OptiConnect method, or the Extended Function Path OptiConnect method.
|
||
|
|
The Fastpath OptiConnect method is easier to begin using, but you cannot
|
||
|
|
use commitment control, or Distributed Unit of Work (*DUW) for the connect
|
||
|
|
method. If commitment control or *DUW is needed, you will need to route SQL
|
||
|
|
over OptiConnect by using the Extended Function Path method.</p>
|
||
|
|
<p>OptiConnect supports the use of static Structured Query Language (SQL)
|
||
|
|
with both Dynamic, and Extended Dynamic SQL. You can also route Extended Dynamic
|
||
|
|
SQL statements over OptiConnect by using the QXDA set of APIs. For more information,
|
||
|
|
see the <a href="../rzahg/rzahgbackup.htm">Backup and Recovery</a> topic.</p>
|
||
|
|
<p><span class="bold">Routing SQL using the fastpath OptiConnect method</span></p>
|
||
|
|
<p>To route SQL requests over OptiConnect using the Fastpath OptiConnect method,
|
||
|
|
you need to specify special keywords in the relational database (RDB) directory.
|
||
|
|
The database system must have an RDB entry that matches the relational database
|
||
|
|
name specified on the application systems with *LOCAL for the remote location
|
||
|
|
parameter. On the application systems, the remote location parameter must
|
||
|
|
point to the system where the database resides. Each relational database name
|
||
|
|
must be unique within the distributed network. Each entry identifies the
|
||
|
|
method of accessing the relational database as well as other parameters.</p>
|
||
|
|
<p>To add an entry to the relational database directory:</p>
|
||
|
|
<ol type="1">
|
||
|
|
<li>Enter the Add Relational Database Directory Entry (ADDRDBDIRE) command</li>
|
||
|
|
<li>Press F4=Prompt</li>
|
||
|
|
<li>Press F9=Show all parameters</li></ol>
|
||
|
|
<ol type="1">
|
||
|
|
<li>Enter a name for the <span class="italic">Relational database</span> parameter.
|
||
|
|
|
||
|
|
<p>The name on the application system <span class="bold">must</span> match the
|
||
|
|
name on the database system.</p></li>
|
||
|
|
<li>Enter the <span class="italic">Remote location</span> parameter.
|
||
|
|
<p>On each
|
||
|
|
application system, specify the name of the target system. On the database
|
||
|
|
system, specify *LOCAL.</p></li>
|
||
|
|
<li>Enter QYCTSOC for the<span class="italic"> APPC device description</span>.</li>
|
||
|
|
<li>Enter *LOC for <span class="italic">Local location</span>.</li></ol>
|
||
|
|
<p>After creating the relational database directory entry, you will need to
|
||
|
|
recompile the SQL program to point to the RDB entry. When recompiling specify:</p>
|
||
|
|
<ol type="1">
|
||
|
|
<li>Commitment Control *NONE</li>
|
||
|
|
<li>RDB connect method *RUW</li></ol>
|
||
|
|
<a name="wq27"></a>
|
||
|
|
<div class="notetitle" id="wq27">Note:</div>
|
||
|
|
<div class="notebody">The relational database parameter has to match the relational
|
||
|
|
database parameter in the RDB entry.</div>
|
||
|
|
<p><span class="bold">Route SQL using the Extended Function Path Method</span></p>
|
||
|
|
<p>To route SQL requests over OptiConnect using the Extended Function Path
|
||
|
|
method, you need to specify the Remote location and Local location in the
|
||
|
|
relational database (RDB) directory. Ensure that these match the Extended
|
||
|
|
Function Path descriptions (previously created in <a href="rzau3ctld.htm#ctld">Configure extended function path routing</a>).</p>
|
||
|
|
<p>Recompiling the SQL program pulls the target system name from the RDB entry,
|
||
|
|
creates an SQL package, and runs the program on the target system.</p>
|
||
|
|
<a id="Bot_Of_Page" name="Bot_Of_Page"></a>
|
||
|
|
</body>
|
||
|
|
</html>
|