79 lines
6.0 KiB
HTML
79 lines
6.0 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="Customization of data distribution with DB2 Multisystem" />
|
|
<meta name="abstract" content="Because the system is responsible for placing the data, you do not need to know where the records actually reside. However, if you want to guarantee that certain records are always stored on a particular system, you can use the Change Node Group Attributes (CHGNODGRPA) command to specify where those records reside." />
|
|
<meta name="description" content="Because the system is responsible for placing the data, you do not need to know where the records actually reside. However, if you want to guarantee that certain records are always stored on a particular system, you can use the Change Node Group Attributes (CHGNODGRPA) command to specify where those records reside." />
|
|
<meta name="DC.subject" content="data distribution, customizing, Change Physical File (CHGPF) command, data distribution, customizing, command, CL, CHGPF (Change Physical File), data distribution, customizing, Change Physical File (CHGPF), CHGPF (Change Physical File) command" />
|
|
<meta name="keywords" content="data distribution, customizing, Change Physical File (CHGPF) command, data distribution, customizing, command, CL, CHGPF (Change Physical File), data distribution, customizing, Change Physical File (CHGPF), CHGPF (Change Physical File) command" />
|
|
<meta name="DC.Relation" scheme="URI" content="crtdf.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="chgnga.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="planpart.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="scali.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="custdd" />
|
|
<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>Customization of data distribution with DB2 Multisystem</title>
|
|
</head>
|
|
<body id="custdd"><a name="custdd"><!-- --></a>
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|
<h1 class="topictitle1">Customization of data distribution with DB2<sup>®</sup> Multisystem</h1>
|
|
<div><p>Because the system is responsible for placing the data, you do
|
|
not need to know where the records actually reside. However, if you want to
|
|
guarantee that certain records are always stored on a particular system, you
|
|
can use the Change Node Group Attributes (CHGNODGRPA) command to specify where
|
|
those records reside.</p>
|
|
<p>As an example, suppose you want all the records for the
|
|
55902 ZIP code to reside on your system in Minneapolis, Minnesota. When you
|
|
issue the CHGNODGRPA command, you should specify the 55902 ZIP code and the
|
|
system node number of the local node in Minneapolis.</p>
|
|
<p>At this point, the 55902 ZIP has changed node groups, but the data is still
|
|
distributed as it was previously. The CHGNODGRPA command does not affect the
|
|
existing files. When a partitioned file is created, the partitioned file keeps
|
|
a copy of the information from the node group at that time. The node group
|
|
can be changed or deleted without affecting the partitioned file. For the
|
|
changes to the records that are to be redistributed to take effect, either
|
|
you can re-create the distributed file using the new node group,
|
|
or you can use the Change Physical File (CHGPF) command and specify the new
|
|
or updated node group.</p>
|
|
<p>Using the CHGPF command, you can:</p>
|
|
<ul><li>Redistribute an already partitioned file</li>
|
|
<li>Change a partitioning key (from the telephone area code to the branch
|
|
ID, for example)</li>
|
|
<li>Change a local file to be a distributed file</li>
|
|
<li>Change a distributed file to a local file.</li>
|
|
</ul>
|
|
<div class="note"><span class="notetitle">Note:</span> You must also use the CHGNODGRPA command to redistribute an already
|
|
partitioned file. The CHGNODGRPA command can be optionally used with the CHGPF
|
|
command to do any of the other tasks.</div>
|
|
<p>See Redistribution issues for adding systems to a network for information
|
|
on changing a local file to a distributed file or a distributed file to a
|
|
local file.</p>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="crtdf.htm" title="A distributed file is a database file that is spread across multiple iSeries servers.">Distributed files with DB2 Multisystem</a></div>
|
|
</div>
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
|
<div><a href="chgnga.htm" title="The Change Node Group Attributes (CHGNODGRPA) command changes the data partitioning attributes for a node group.">Change Node Group Attributes (CHGNODGRPA) command</a></div>
|
|
<div><a href="planpart.htm" title="In most cases, you should plan ahead to determine how you want to use partitioning and partitioning keys.">Plan for partitioning with DB2 Multisystem</a></div>
|
|
<div><a href="scali.htm" title="The redistribution of a file across a node group is a fairly simple process.">Redistribution issues for adding systems to a network</a></div>
|
|
</div>
|
|
</div>
|
|
</body>
|
|
</html> |