106 lines
7.6 KiB
HTML
106 lines
7.6 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="reference" />
|
||
|
|
<meta name="DC.Title" content="User databases on independent auxiliary storage pools" />
|
||
|
|
<meta name="abstract" content="The user might create additional relational databases on an iSeries server by configuring independent auxiliary storage pools (IASPs) on the server. Each independent auxiliary storage pool group is a relational database." />
|
||
|
|
<meta name="description" content="The user might create additional relational databases on an iSeries server by configuring independent auxiliary storage pools (IASPs) on the server. Each independent auxiliary storage pool group is a relational database." />
|
||
|
|
<meta name="DC.subject" content="user exit program, DDM" />
|
||
|
|
<meta name="keywords" content="user exit program, DDM" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbal1setup.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../cl/dspneta.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../rzaig/rzaigconfigipaddrressapp.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../db2/rbafzmst02.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../rzakj/rzakjtrouble.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbal1rdbdir.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="rbal1drdaconsiderations" />
|
||
|
|
<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>User databases on independent auxiliary storage pools</title>
|
||
|
|
</head>
|
||
|
|
<body id="rbal1drdaconsiderations"><a name="rbal1drdaconsiderations"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">User databases on independent auxiliary storage pools</h1>
|
||
|
|
<div><p>The user might create additional relational databases on an <span class="keyword">iSeries™</span> server by configuring independent
|
||
|
|
auxiliary storage pools (IASPs) on the server. Each independent auxiliary
|
||
|
|
storage pool group is a relational database.</p>
|
||
|
|
<div class="section"><p>In this topic, independent auxiliary storage pool groups are called
|
||
|
|
user databases. They consist of all the database objects that exist on the
|
||
|
|
independent auxiliary storage pool group disks. Additionally, all database
|
||
|
|
objects in the system relational database (called system database in this
|
||
|
|
topic collection) of the iSeries server to which the independent auxiliary
|
||
|
|
storage pool is varied on are logically included in a user relational database.
|
||
|
|
However, from a commitment control perspective, the system database is treated
|
||
|
|
differently.</p>
|
||
|
|
</div>
|
||
|
|
<div class="section"><p>There are a number of rules associated with the creation and use
|
||
|
|
of user databases, besides those imposed by the commitment control considerations
|
||
|
|
just mentioned. One example is that you cannot use an Advanced Program-to-Program
|
||
|
|
Communication (APPC) protected distributed unit of work (DUW) conversation
|
||
|
|
to connect to a database from an application requester (AR) which has been
|
||
|
|
set to a user database (an auxiliary storage pool [ASP] group) for the current
|
||
|
|
thread. Another example is that the name of any schema created in a user database
|
||
|
|
must not already exist in that user database or in the associated system database.
|
||
|
|
For more information about such restrictions, see the SQL reference topic.</p>
|
||
|
|
</div>
|
||
|
|
<div class="section"><p>There are certain DRDA-related objects that cannot be contained
|
||
|
|
in user databases. DDM user exit programs must reside in libraries in the
|
||
|
|
system database, as must any Application Requester Driver programs. </p>
|
||
|
|
</div>
|
||
|
|
<div class="section"><p>You should be aware that the process of varying on a user database
|
||
|
|
causes the RDB directory to be unavailable for a period of time, which can
|
||
|
|
cause attempts by a DRDA<sup>®</sup> application requester or application server (AS)
|
||
|
|
to make use of the directory to be delayed or to timeout. The exposure to
|
||
|
|
having directory operations timeout due to unavailability caused by varying
|
||
|
|
on a database is much greater if multiple databases are varied on at the same
|
||
|
|
time. As noted here, the first time a user database is varied on, an attempt
|
||
|
|
is made by the server to add a directory entry for that database. If the directory
|
||
|
|
is unavailable due to a concurrent vary on operation, the addition will fail,
|
||
|
|
in which case the entry will have to be manually added.</p>
|
||
|
|
</div>
|
||
|
|
<div class="section"><p>Other considerations in the use of user databases concern configuration
|
||
|
|
of entries in the RDB directory. One of the rules for naming user databases
|
||
|
|
is that user RDB names cannot match the system name specified in the network
|
||
|
|
attributes (as displayed by the <span class="cmdname">Display Network Attributes (DSPNETA)</span> command). </p>
|
||
|
|
</div>
|
||
|
|
<div class="section"><p>Local user database entries in the RDB directory are added automatically
|
||
|
|
the first time that the associated databases are varied on. They are created
|
||
|
|
using the *IP protocol type and with the remote location designated as LOOPBACK.
|
||
|
|
LOOPBACK indicates that the database is on the same server as the directory.
|
||
|
|
It is highly recommended that user databases that are intended to be switched
|
||
|
|
among servers be configured to have a dedicated IP address associated with
|
||
|
|
them. If the switchable database does not have a dedicated IP address, then
|
||
|
|
whenever it is switched, manual updating of its directory entry on all the
|
||
|
|
servers that reference that database must be done.</p>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbal1setup.htm" title="The runtime support for an iSeries distributed relational database is provided by the operating system. Therefore, when the operating system is installed, distributed relational database support is installed.">Initial setup</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
||
|
|
<div><a href="../rzaig/rzaigconfigipaddrressapp.htm">Manage application CRG IP addresses</a></div>
|
||
|
|
<div><a href="../rzakj/rzakjtrouble.htm">Troubleshoot transactions and commitment control</a></div>
|
||
|
|
<div><a href="rbal1rdbdir.htm" title="The i5/OS licensed program uses the relational database directory to define the relational database names that can be accessed by applications running on an iSeries server, to specify if the connection uses Systems Network Architecture (SNA) or IP, and to associate these relational database names with their corresponding network parameters.">Use the relational database directory</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relref"><strong>Related reference</strong><br />
|
||
|
|
<div><a href="../cl/dspneta.htm">Display Network Attributes (DSPNETA) command</a></div>
|
||
|
|
<div><a href="../db2/rbafzmst02.htm">SQL reference</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|