139 lines
8.3 KiB
HTML
139 lines
8.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="Add an entry for SNA usage" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbal1workwith.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../cl/addrdbdire.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbal1tpn1.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbal1tpn2.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbal1tpn3.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbal1tpn4.htm" />
|
||
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 1998, 2006" />
|
||
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 1998, 2006" />
|
||
|
|
<meta name="DC.Format" content="XHTML" />
|
||
|
|
<meta name="DC.Identifier" content="rbal1addsna" />
|
||
|
|
<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>Add an entry for SNA usage</title>
|
||
|
|
</head>
|
||
|
|
<body id="rbal1addsna"><a name="rbal1addsna"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Add an entry for SNA usage</h1>
|
||
|
|
<div><div class="p">The <span class="cmdname">Add RDB Directory Entry (ADDRDBDIRE)</span> display is
|
||
|
|
shown here. You can use the prompts in this display or the <span class="cmdname">Add Relational
|
||
|
|
Database Directory Entry (ADDRDBDIRE)</span> command to add an entry to
|
||
|
|
the relational database directory. <pre class="screen">Add RDB Directory Entry (ADDRDBDIRE)
|
||
|
|
|
||
|
|
Type choices, press Enter.
|
||
|
|
|
||
|
|
Relational database . . . . . . MP311 Name
|
||
|
|
Relational database alias . . . *NONE
|
||
|
|
Remote location:
|
||
|
|
Name or address . . . . . . . MP311 Name, *LOCAL, *ARDPGM
|
||
|
|
Type . . . . . . . . . . . . . *SNA *SNA, *IP
|
||
|
|
Text . . . . . . . . . . . . . . 'Oak Street Dealership'
|
||
|
|
</pre>
|
||
|
|
</div>
|
||
|
|
<div class="section"><p>In this example, an entry is made to add a relational database
|
||
|
|
named MP311 for a server with a remote location name of MP311 to the relational
|
||
|
|
database directory on the local server. For SNA connections, the relational
|
||
|
|
database alias field must be left with its *NONE default value. The remote
|
||
|
|
location name does not have to be defined before a relational database directory
|
||
|
|
entry using it is created. However, the remote location name must be defined
|
||
|
|
before the relational database directory entry is used in an application.
|
||
|
|
The relational database name (RDB) parameter and the remote location name
|
||
|
|
(RMTLOCNAME) parameter are required for the <span class="cmdname">Add Relational Database
|
||
|
|
Directory Entry (ADDRDBDIRE)</span> command. The second element of the
|
||
|
|
RMTLOCNAME parameter defaults to *SNA. The descriptive text (TEXT) parameter
|
||
|
|
is optional. As shown in this example, it is a good idea to make the relational
|
||
|
|
database name the same as the server name or location name specified for this
|
||
|
|
server in your network configuration. This can help you identify a database
|
||
|
|
name and correlate it to a particular server in your distributed relational
|
||
|
|
database network, especially if your network is complex.</p>
|
||
|
|
</div>
|
||
|
|
<div class="section"><div class="p">To see the other optional parameters on this command, press F10
|
||
|
|
on the <span class="cmdname">Add RDB Directory Entry (ADDRDBDIRE)</span> display. These
|
||
|
|
optional parameters are shown here. <pre class="screen">Add RDB Directory Entry (ADDRDBDIRE)
|
||
|
|
|
||
|
|
Type choices, press Enter.
|
||
|
|
|
||
|
|
Relational database . . . . . . MP311
|
||
|
|
Relational database alias . . . *NONE
|
||
|
|
Remote location
|
||
|
|
Name or address . . . . . . . MP311
|
||
|
|
Type . . . . . . . . . . . . . *SNA *SNA, *IP
|
||
|
|
Text . . . . . . . . . . . . . . 'Oak Street Dealership'
|
||
|
|
|
||
|
|
Device:
|
||
|
|
APPC device description . . . *LOC Name, *LOC
|
||
|
|
Local location . . . . . . . . . *LOC Name, *LOC, *NETATR
|
||
|
|
Remote network identifier . . . *LOC Name, *LOC, *NETATR, *NONE
|
||
|
|
Mode . . . . . . . . . . . . . . *NETATR Name, *NETATR
|
||
|
|
Transaction program . . . . . . *DRDA Character value, *DRDA
|
||
|
|
</pre>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div class="section"><p>The server provides default *SNA values for the additional <span class="cmdname">Add
|
||
|
|
Relational Database Directory Entry (ADDRDBDIRE)</span> command parameters: </p>
|
||
|
|
<ul><li>Device (DEV)</li>
|
||
|
|
<li>Local location (LCLLOCNAME)</li>
|
||
|
|
<li>Remote network identifier (RMTNETID)</li>
|
||
|
|
<li>Mode (MODE)</li>
|
||
|
|
<li>Transaction program (TNSPGM)</li>
|
||
|
|
</ul>
|
||
|
|
</div>
|
||
|
|
<div class="section"><div class="note"><span class="notetitle">Notes:</span> <ol><li>For SNA connections, the relational database alias field must be left
|
||
|
|
with its *NONE default value.</li>
|
||
|
|
<li>The transaction program name parameter in the <span class="keyword">iSeries™ server</span> is
|
||
|
|
TNSPGM. In SNA, it is TPN.</li>
|
||
|
|
<li>If you use the defaults with Advanced Program-to-Program Communication
|
||
|
|
(APPC), the server determines the device, the local location, and the remote
|
||
|
|
network identifier that will be used. The mode name defined in the network
|
||
|
|
attributes is used and the transaction program name for Distributed
|
||
|
|
Relational Database Architecture™ (DRDA<sup>®</sup>) support is used. If you use the defaults
|
||
|
|
with Advanced
|
||
|
|
Peer-to-Peer Networking<sup>®</sup> (APPN), the server ignores the device (DEV) parameter,
|
||
|
|
and uses the local location name, remote network identifier, and mode name
|
||
|
|
defined in the network attributes.</li>
|
||
|
|
</ol>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div class="section"><p>You can change any of these default values on the Add Relational
|
||
|
|
Database Directory Entry (ADDRDBDIRE) command. For example, you might have
|
||
|
|
to change the TNSPGM parameter to communicate with an DB2 Universal Database™ for
|
||
|
|
VM server. By default for DB2 Universal Database for VM support,
|
||
|
|
the TNSPGM is the name of the DB2 Universal Database for
|
||
|
|
VM database to which you want to connect. The default TNSPGM parameter value
|
||
|
|
for DRDA (*DRDA)
|
||
|
|
is <span>X'07F6C4C2'</span>. QCNTEDDM and DB2DRDA also map to <span>X'07F6C4C2'</span>.
|
||
|
|
For more information about transaction program name, see the related topics.</p>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbal1workwith.htm" title="Use these instructions to work with the relational database directory.">Work with the relational database directory</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="reltasks"><strong>Related tasks</strong><br />
|
||
|
|
<div><a href="rbal1tpn2.htm" title="Change the UCOMDIR NAMES file to specify QCNTSRVC in the TPN tag.">Set QCNTSRVC as a TPN on a DB2 Universal Database for VM application requester</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relref"><strong>Related reference</strong><br />
|
||
|
|
<div><a href="../cl/addrdbdire.htm">Add Relational Database Directory Entry (ADDRDBDIRE) command</a></div>
|
||
|
|
<div><a href="rbal1tpn1.htm" title="Specify the QCNTSRVC on the TNSPGM parameter of the Add Relational Database Directory Entry (ADDRDBDIRE) or Change Relational Database Directory Entry (CHGRDBDIRE) command.">Set QCNTSRVC as a TPN on a DB2 Universal Database for iSeries application requester</a></div>
|
||
|
|
<div><a href="rbal1tpn3.htm" title="Update the SYSIBM.LOCATIONS table to specify QCNTSRVC in the TPN column for the row that contains the RDB-NAME of the DB2 Universal Database for iSeries application server.">Set QCNTSRVC as a TPN on a DB2 Universal Database for z/OS application requester</a></div>
|
||
|
|
<div><a href="rbal1tpn4.htm" title="If you are working with DB2 Universal Database for Linux, UNIX and Windows and would like instructions on how to set up the TPN on this family of products, there is a Web page to help you.">Set QCNTSRVC as a TPN on a DB2 Universal Database for Linux, UNIX and Windows application requester</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|