69 lines
5.4 KiB
HTML
69 lines
5.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="Introduction of node groups with DB2 Multisystem" />
|
|
<meta name="abstract" content="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." />
|
|
<meta name="description" content="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." />
|
|
<meta name="DC.subject" content="node group, introduction to, introduction, node groups" />
|
|
<meta name="keywords" content="node group, introduction to, introduction, node groups" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzaf3kickoff.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="nodework.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="prenodetask.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="crtngc.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="dspng.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="chgnga.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="deletenode.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="RZAF3C2-gen4" />
|
|
<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>Introduction of node groups with DB2 Multisystem</title>
|
|
</head>
|
|
<body id="RZAF3C2-gen4"><a name="RZAF3C2-gen4"><!-- --></a>
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|
<h1 class="topictitle1">Introduction of node groups with DB2<sup>®</sup> Multisystem</h1>
|
|
<div><p>To enable database files to be visible across a set of <span class="keyword">iSeries™</span> servers, you must first define
|
|
the group of systems (node group) that you want the files on.</p>
|
|
<p>A node group can have 2 to 32 nodes defined for it. The number of nodes
|
|
that is defined for the node group determines the number of systems across
|
|
which the database file is created. The local system must be one of the systems
|
|
that is specified in the node group. When the system creates the node group,
|
|
the system assigns a number, starting with number 1, to each node.</p>
|
|
</div>
|
|
<div>
|
|
<ul class="ullinks">
|
|
<li class="ulchildlink"><strong><a href="nodework.htm">How node groups work with DB2 Multisystem</a></strong><br />
|
|
A <em>node group</em> is a system object (*NODGRP), which is stored
|
|
on the system on which it was created.</li>
|
|
<li class="ulchildlink"><strong><a href="prenodetask.htm">Tasks to complete before using the node group commands with DB2 Multisystem</a></strong><br />
|
|
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.</li>
|
|
<li class="ulchildlink"><strong><a href="crtngc.htm">Create Node Group (CRTNODGRP) command</a></strong><br />
|
|
This section uses two CL command examples to show how to create a node group by using the Create Node Group (CRTNODGRP) command.</li>
|
|
<li class="ulchildlink"><strong><a href="dspng.htm">Display Node Group (DSPNODGRP) command</a></strong><br />
|
|
The Display Node Group (DSPNODGRP) command displays the nodes (systems) in a node group.</li>
|
|
<li class="ulchildlink"><strong><a href="chgnga.htm">Change Node Group Attributes (CHGNODGRPA) command</a></strong><br />
|
|
The Change Node Group Attributes (CHGNODGRPA) command changes the data partitioning attributes for a node group.</li>
|
|
<li class="ulchildlink"><strong><a href="deletenode.htm">Delete Node Group (DLTNODGRP) command</a></strong><br />
|
|
The Delete Node Group (DLTNODGRP) command deletes a previously created node group.</li>
|
|
</ul>
|
|
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaf3kickoff.htm" title="This topic describes the fundamental concepts of DB2 Multisystem, such as distributed relational database files, node groups, and partitioning, and provides the information necessary to create and to use database files that are partitioned across multiple iSeries servers. Information is provided on how to configure the systems, how to create the files, and how the files can be used in applications. This topic also describes table partitioning. Table partitioning varies from multisystem partitioning in that it is a table partitioned on a single server.">DB2 Multisystem</a></div>
|
|
</div>
|
|
</div>
|
|
</body>
|
|
</html> |