72 lines
6.4 KiB
HTML
72 lines
6.4 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="Tasks to complete before using the node group commands with DB2 Multisystem" />
|
||
|
|
<meta name="abstract" content="Before using the Create Node Group (CRTNODGRP) command or any of the node group commands, you must ensure that the distributed relational database network you are using has been properly set up." />
|
||
|
|
<meta name="description" content="Before using the Create Node Group (CRTNODGRP) command or any of the node group commands, you must ensure that the distributed relational database network you are using has been properly set up." />
|
||
|
|
<meta name="DC.subject" content="distributed relational database network, setting up, local (*LOCAL) system, distributed relational database network, defining local (*LOCAL) system, defining in distributed relational database network, WRKRDBDIRE (Work with RDB Directory Entries) command, Work with RDB Directory Entries (WRKRDBDIRE) command, command, CL, WRKRDBDIRE (Work with RDB Directory Entries) command, command, CL, Work with RDB Directory Entries (WRKRDBDIRE) command, RMTLOCNAME (remote location name) parameter, remote location name (RMTLOCNAME) parameter, ADDRDBDIRE (Add RDB Directory Entries) command, Add RDB Directory Entries (ADDRDBDIRE) command, ADDRDBDIRE (Add RDB Directory Entries), Add RDB Directory Entries (ADDRDBDIRE), node group commands, tasks to complete before using" />
|
||
|
|
<meta name="keywords" content="distributed relational database network, setting up, local (*LOCAL) system, distributed relational database network, defining local (*LOCAL) system, defining in distributed relational database network, WRKRDBDIRE (Work with RDB Directory Entries) command, Work with RDB Directory Entries (WRKRDBDIRE) command, command, CL, WRKRDBDIRE (Work with RDB Directory Entries) command, command, CL, Work with RDB Directory Entries (WRKRDBDIRE) command, RMTLOCNAME (remote location name) parameter, remote location name (RMTLOCNAME) parameter, ADDRDBDIRE (Add RDB Directory Entries) command, Add RDB Directory Entries (ADDRDBDIRE) command, ADDRDBDIRE (Add RDB Directory Entries), Add RDB Directory Entries (ADDRDBDIRE), node group commands, tasks to complete before using" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaf3c2-gen4.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../ddp/rbal1kickoff.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="prenodetask" />
|
||
|
|
<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>Tasks to complete before using the node group commands with DB2 Multisystem</title>
|
||
|
|
</head>
|
||
|
|
<body id="prenodetask"><a name="prenodetask"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Tasks to complete before using the node group commands with DB2 Multisystem</h1>
|
||
|
|
<div><p>Before using the Create Node Group (CRTNODGRP) command or any of
|
||
|
|
the node group commands, you must ensure that the distributed relational database
|
||
|
|
network you are using has been properly set up.</p>
|
||
|
|
<p>If this is a new distributed relational database network, see Distributed
|
||
|
|
Database Programming for information about establishing the network.</p>
|
||
|
|
<div class="p">You need to ensure that one system in the network is defined as the local
|
||
|
|
(*LOCAL) system. Use the Work with RDB (Relational Database) Directory Entries
|
||
|
|
(WRKRDBDIRE) command to display the details about the entries. If a local
|
||
|
|
system is not defined, you can do so by specifying *LOCAL for the remote location
|
||
|
|
name (RMTLOCNAME) parameter of the Add RDB Directory Entries (ADDRDBDIRE)
|
||
|
|
command, for example: <pre> ADDRDBDIRE RDB(MP000) RMTLOCNAME(*LOCAL) TEXT ('New York')</pre>
|
||
|
|
</div>
|
||
|
|
<p>The <span class="keyword">iSeries™</span> server in New
|
||
|
|
York, named MP000, is defined as the local system in the relational database
|
||
|
|
directory. You can have only one local relational database defined on an <span class="keyword">iSeries</span> server as the system name or
|
||
|
|
local location name specified for this system in your network configuration.
|
||
|
|
This can help you identify a database name and correlate it to a particular
|
||
|
|
system in your distributed relational database network, especially if your
|
||
|
|
network is complex.</p>
|
||
|
|
<p>For <span class="keyword">DB2<sup>®</sup> Multisystem</span> to properly
|
||
|
|
distribute files to the <span class="keyword">iSeries</span> servers
|
||
|
|
within the node groups that you define, you must have the remote database
|
||
|
|
(RDB) names consistent across all the nodes (systems) in the node group.</p>
|
||
|
|
<p>For example, if you plan to have three systems in your node group, each
|
||
|
|
system must have at least three entries in the RDB directory. On each system,
|
||
|
|
the three names must all be the same. On each of the three systems, an entry
|
||
|
|
exists for the local system, which is identified as *LOCAL. The other two
|
||
|
|
entries contain the appropriate remote location information.</p>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaf3c2-gen4.htm" title="To enable database files to be visible across a set of iSeries servers, you must first define the group of systems (node group) that you want the files on.">Introduction of node groups with DB2 Multisystem</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
||
|
|
<div><a href="../ddp/rbal1kickoff.htm">Distributed database programming</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|