79 lines
5.8 KiB
HTML
79 lines
5.8 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="Scalar functions available with DB2 Multisystem" />
|
||
|
|
<meta name="abstract" content="For DB2 Multisystem, scalar functions are available when you work with distributed files." />
|
||
|
|
<meta name="description" content="For DB2 Multisystem, scalar functions are available when you work with distributed files." />
|
||
|
|
<meta name="DC.subject" content="scalar function, SQL, scalar functions, OPNQRYF (Open Query File) command, Open Query File (OPNQRYF) command" />
|
||
|
|
<meta name="keywords" content="scalar function, SQL, scalar functions, OPNQRYF (Open Query File) command, Open Query File (OPNQRYF) command" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaf3kickoff.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="scalarpart.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="scalarhash.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="scalarnodename.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="scalarnodenumber.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="spreg.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../db2/rbafzmst02.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../rbam6/rbam6clmain.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="RZAF3C4-gen5" />
|
||
|
|
<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>Scalar functions available with DB2 Multisystem</title>
|
||
|
|
</head>
|
||
|
|
<body id="RZAF3C4-gen5"><a name="RZAF3C4-gen5"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Scalar functions available with DB2 Multisystem</h1>
|
||
|
|
<div><p>For DB2<sup>®</sup> Multisystem,
|
||
|
|
scalar functions are available when you work with distributed files.</p>
|
||
|
|
<p>These functions help you determine how to distribute the data in your files
|
||
|
|
as well as determine where the data is after the file has been distributed.
|
||
|
|
When working with distributed files, database administrators might
|
||
|
|
find these functions to be helpful debugging tools.</p>
|
||
|
|
<p>These scalar functions are PARTITION, HASH, NODENAME, and NODENUMBER. You
|
||
|
|
can use these functions through SQL or the Open Query File (OPNQRYF) command.</p>
|
||
|
|
<p>For information about the syntax of the SQL scalar functions, see the SQL
|
||
|
|
Reference. For information about syntax of the OPNQRYF scalar functions, see
|
||
|
|
the Control language topic in the information center.</p>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<ul class="ullinks">
|
||
|
|
<li class="ulchildlink"><strong><a href="scalarpart.htm">PARTITION with DB2 Multisystem</a></strong><br />
|
||
|
|
Through the PARTITION function, you can determine the partition number where a specific row of the distributed relational database is stored.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="scalarhash.htm">HASH with DB2 Multisystem</a></strong><br />
|
||
|
|
The HASH function returns the partition number by applying the hash function to the specified expressions.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="scalarnodename.htm">NODENAME with DB2 Multisystem</a></strong><br />
|
||
|
|
Through the NODENAME function, you can determine the name of the relational database (RDB) where a specific row of the distributed relational database is stored.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="scalarnodenumber.htm">NODENUMBER with DB2 Multisystem</a></strong><br />
|
||
|
|
Through the NODENUMBER function, you can determine the node number where a specific row of the distributed relational database is stored.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="spreg.htm">Special registers with DB2 Multisystem</a></strong><br />
|
||
|
|
For DB2 Multisystem,
|
||
|
|
all instances of special registers are resolved on the coordinator node before
|
||
|
|
sending the query to the remote nodes. (A <em>coordinator node</em> is
|
||
|
|
the system on which the query was initiated.) This way, all nodes run the
|
||
|
|
query with consistent special register values.</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 class="relref"><strong>Related reference</strong><br />
|
||
|
|
<div><a href="../db2/rbafzmst02.htm">SQL reference</a></div>
|
||
|
|
<div><a href="../rbam6/rbam6clmain.htm">Control language</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|