60 lines
4.6 KiB
HTML
60 lines
4.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="concept" />
|
||
|
|
<meta name="DC.Title" content="Commitment control and independent disk pools" />
|
||
|
|
<meta name="abstract" content="Independent disk pools and independent disk pool groups, can each have a separate i5/OS SQL database. You can use commitment control with these databases." />
|
||
|
|
<meta name="description" content="Independent disk pools and independent disk pool groups, can each have a separate i5/OS SQL database. You can use commitment control with these databases." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakjconcepts.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakjconsidcdef.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakjconsidxa.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakjcommitdef.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakjlocalremote.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakjprotocol.htm" />
|
||
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 2004, 2006" />
|
||
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 2004, 2006" />
|
||
|
|
<meta name="DC.Format" content="XHTML" />
|
||
|
|
<meta name="DC.Identifier" content="rzakjiasp" />
|
||
|
|
<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>Commitment control and independent disk pools</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzakjiasp"><a name="rzakjiasp"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Commitment control and independent disk pools</h1>
|
||
|
|
<div><p>Independent disk pools and independent disk pool groups, can each
|
||
|
|
have a separate i5/OS™ SQL
|
||
|
|
database. You can use commitment control with these databases. </p>
|
||
|
|
<p>However, because each independent disk pool or independent disk pool group
|
||
|
|
has a separate SQL database, you should be aware of some considerations.</p>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<ul class="ullinks">
|
||
|
|
<li class="ulchildlink"><strong><a href="rzakjconsidcdef.htm">Independent disk pool considerations for commitment definitions</a></strong><br />
|
||
|
|
You must be aware of the considerations for commitment definitions in this topic when you use independent disk pools.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzakjconsidxa.htm">Considerations for XA transactions</a></strong><br />
|
||
|
|
In the XA environment, each database is considered a separate resource manager. When a transaction manager wants to access two databases under the same transaction, it must use the XA protocols to perform two-phase commit with the two resource managers.</li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzakjconcepts.htm" title="This topic provides information to help you understand how commitment control works, how it interacts with your system, and how it interacts with other systems in your network.">Commitment control concepts</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
||
|
|
<div><a href="rzakjcommitdef.htm" title="You create a commitment definition when you use the Start Commitment Control (STRCMTCTL) command to start commitment control on your system. Also, DB2 Universal Database (UDB) for iSeries automatically creates a commitment definition when the isolation level is other than No Commit.">Commitment definition</a></div>
|
||
|
|
<div><a href="rzakjlocalremote.htm" title="A committable resource can be either a local resource or a remote resource.">Local and remote committable resources</a></div>
|
||
|
|
<div><a href="rzakjprotocol.htm" title="Commit protocol is the capability a resource has to participate in one-phase or two-phase commit processing. Local resources, except API committable resources, are always two-phase resources.">The commit protocol of a committable resource</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|