80 lines
6.7 KiB
HTML
80 lines
6.7 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="How node groups work with DB2 Multisystem" />
|
||
|
<meta name="abstract" content="A node group is a system object (*NODGRP), which is stored on the system on which it was created." />
|
||
|
<meta name="description" content="A node group is a system object (*NODGRP), which is stored on the system on which it was created." />
|
||
|
<meta name="DC.subject" content="node group, *NODGRP system object, partitioning, default partitioning, partition number, hash algorithm, default partitioning, system object, *NODGRP, CRTNODGRP (Create Node Group) command, changing data partitioning, Create Node Group (CRTNODGRP) command, command, CL, CRTNODGRP (Create Node Group), changing data partitioning, Create Node Group (CRTNODGRP), PTNFILE (partitioning file) parameter, partitioning file (PTNFILE) parameter, CHGNODGRPA (Change Node Group Attributes) command, Change Node Group Attributes (CHGNODGRPA) command, CHGNODGRPA (Change Node Group Attributes), Change Node Group Attributes (CHGNODGRPA), node group, changing" />
|
||
|
<meta name="keywords" content="node group, *NODGRP system object, partitioning, default partitioning, partition number, hash algorithm, default partitioning, system object, *NODGRP, CRTNODGRP (Create Node Group) command, changing data partitioning, Create Node Group (CRTNODGRP) command, command, CL, CRTNODGRP (Create Node Group), changing data partitioning, Create Node Group (CRTNODGRP), PTNFILE (partitioning file) parameter, partitioning file (PTNFILE) parameter, CHGNODGRPA (Change Node Group Attributes) command, Change Node Group Attributes (CHGNODGRPA) command, CHGNODGRPA (Change Node Group Attributes), Change Node Group Attributes (CHGNODGRPA), node group, changing" />
|
||
|
<meta name="DC.Relation" scheme="URI" content="rzaf3c2-gen4.htm" />
|
||
|
<meta name="DC.Relation" scheme="URI" content="crtngc.htm" />
|
||
|
<meta name="DC.Relation" scheme="URI" content="ption.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="nodework" />
|
||
|
<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>How node groups work with DB2 Multisystem</title>
|
||
|
</head>
|
||
|
<body id="nodework"><a name="nodework"><!-- --></a>
|
||
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
<h1 class="topictitle1">How node groups work with DB2 Multisystem</h1>
|
||
|
<div><p>A <em>node group</em> is a system object (*NODGRP), which is stored
|
||
|
on the system on which it was created.</p>
|
||
|
<p>A node group is not a distributed object. The *NODGRP system
|
||
|
object contains all the information about the systems in the group as well
|
||
|
as information about how the data in the data files should be partitioned
|
||
|
(distributed). The default partitioning is for each system (node) to receive
|
||
|
an equal share of the data.</p>
|
||
|
<p>The partitioning is handled using a hash algorithm. When a node group
|
||
|
is created, partition numbers ranging from 0 to 1023 are associated with the
|
||
|
node group. With the default partitioning, an equal number of partitions are
|
||
|
assigned to each of the nodes in the node group. When data is added to the
|
||
|
file, the data in the partitioning key is hashed, which results in a partition
|
||
|
number. The entire record of data is not hashed-only the data in the partitioning
|
||
|
key is hashed through the hash algorithm. The node that is associated with
|
||
|
the resulting partition number is where the record of data physically resides.
|
||
|
Therefore, with the default partitioning, each node stores an equal share
|
||
|
of the data, provided that there are enough records of data and a wide range
|
||
|
of values.</p>
|
||
|
<p>If you do not want each node to receive an equal share of the data or if
|
||
|
you want to control which systems have specific pieces of data, you can change
|
||
|
how the data is partitioned, either by specifying a custom partitioning scheme
|
||
|
on the Create Node Group (CRTNODGRP) command using the partition file (PTNFILE)
|
||
|
parameter, or by changing the partitioning scheme later using the Change Node
|
||
|
Group Attributes (CHGNODGRPA) command. Using the PTNFILE parameter, you can
|
||
|
set the node number for each of the partitions within the node group; in other
|
||
|
words, the PTNFILE parameter allows you to tailor how you want data to be
|
||
|
partitioned on the systems in the node group. (The PTNFILE parameter is used
|
||
|
in an example in Creating node groups using the CRTNODGRP command with DB2<sup>®</sup> Multisystem.)
|
||
|
For more information about partitioning, see Partitioning with DB2 Multisystem.</p>
|
||
|
<p>Because a node group is a system object, it can be saved and restored using
|
||
|
the Save Object (SAVOBJ) command and the Restore Object (RSTOBJ) command.
|
||
|
You can restore a node group object either to the system on which it was created
|
||
|
or to any of the systems in the node group. If the node group object is restored
|
||
|
to a system that is not in the node group, the object is unusable.</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="crtngc.htm" title="This section uses two CL command examples to show how to create a node group by using the Create Node Group (CRTNODGRP) command.">Create Node Group (CRTNODGRP) command</a></div>
|
||
|
<div><a href="ption.htm" title="Partitioning is the process of distributing a file across the nodes in a node group.">Partitioning with DB2 Multisystem</a></div>
|
||
|
</div>
|
||
|
</div>
|
||
|
</body>
|
||
|
</html>
|