132 lines
8.5 KiB
HTML
132 lines
8.5 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="Independent disk pool considerations for commitment definitions" />
|
||
|
|
<meta name="abstract" content="You must be aware of the considerations for commitment definitions in this topic when you use independent disk pools." />
|
||
|
|
<meta name="description" content="You must be aware of the considerations for commitment definitions in this topic when you use independent disk pools." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakjiasp.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakjcommitdef.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="rzakjconsidcdef" />
|
||
|
|
<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>Independent disk pool considerations for commitment definitions</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzakjconsidcdef"><a name="rzakjconsidcdef"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Independent disk pool considerations for commitment definitions</h1>
|
||
|
|
<div><p>You must be aware of the considerations for commitment definitions
|
||
|
|
in this topic when you use independent disk pools.</p>
|
||
|
|
<div class="section"><h4 class="sectiontitle">QRECOVERY library considerations</h4><p>When you start
|
||
|
|
commitment control, the commitment definition is created in the QRECOVERY
|
||
|
|
library. Each independent disk pool or independent disk pool group has its
|
||
|
|
own version of a QRECOVERY library. On an independent disk pool, the name
|
||
|
|
of the QRECOVERY library is QRCYxxxxx, where xxxxx is the number of the independent
|
||
|
|
disk pool. For example, the name of the QRECOVERY library for independent
|
||
|
|
disk pool 39 is QRCY00039. Furthermore, if the independent disk pool is part
|
||
|
|
of a disk pool group, only the primary disk pool has a QRCYxxxxx library.</p>
|
||
|
|
<p>When
|
||
|
|
you start commitment control, the commitment definition is created in the
|
||
|
|
QRECOVERY library of the independent disk pool that is associated with that
|
||
|
|
job, making commitment control active on the independent disk pool.</p>
|
||
|
|
</div>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Set ASP Group considerations</h4><p>Using the Set ASP Group
|
||
|
|
(SETASPGRP) command while commitment control is active on an independent disk
|
||
|
|
pool has the following effects:</p>
|
||
|
|
<ul><li>If you switch from an independent disk pool and resources are registered
|
||
|
|
with commitment control on the disk pool, the SETASPGRP command fails with
|
||
|
|
message <span class="msgnum">CPDB8EC</span>, reason code 2, <tt class="msgph">The thread has an
|
||
|
|
uncommitted transaction.</tt> This message is followed by message <span class="msgnum">CPFB8E9</span>.</li>
|
||
|
|
<li>If you switch from an independent disk pool and no resources are registered
|
||
|
|
with commitment control, the commitment definitions are moved to the independent
|
||
|
|
disk pool to which you are switching.</li>
|
||
|
|
<li>If you switch from the system disk pool (ASP group *NONE), commitment
|
||
|
|
control is not affected. The commitment definitions stay on the system disk
|
||
|
|
pool.</li>
|
||
|
|
<li>If you use a notify object, the notify object must reside on the same
|
||
|
|
independent disk pool or independent disk pool group as the commitment definition.</li>
|
||
|
|
<li>If you move the commitment definition to another independent disk pool
|
||
|
|
or independent disk pool group, the notify object must also reside on that
|
||
|
|
other independent disk pool or independent disk pool group. The notify object
|
||
|
|
on the other independent disk pool or independent disk pool group is updated
|
||
|
|
if the commitment definition ends abnormally. If the notify object is not
|
||
|
|
found on the other independent disk pool or independent disk pool group, the
|
||
|
|
update fails with message CPF8358.</li>
|
||
|
|
</ul>
|
||
|
|
</div>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Default journal considerations</h4><p>You should be aware
|
||
|
|
of the following default journal considerations:</p>
|
||
|
|
<ul><li>If you use the default journal, the journal must reside on the same independent
|
||
|
|
disk pool or independent disk pool group as the commitment definition.</li>
|
||
|
|
<li>If the default journal is not found on the other independent disk pool
|
||
|
|
or independent disk pool group when commitment control starts, the commitment
|
||
|
|
control start fails with message CPF9873.</li>
|
||
|
|
<li>If you move the commitment definition to another independent disk pool
|
||
|
|
or independent disk pool group, the default journal must also reside on that
|
||
|
|
other independent disk pool or independent disk pool group. If the journal
|
||
|
|
is not found on the other independent disk pool or independent disk pool group,
|
||
|
|
the commitment definition is moved, but no default journal is used from this
|
||
|
|
point on.</li>
|
||
|
|
</ul>
|
||
|
|
</div>
|
||
|
|
<div class="section"><h4 class="sectiontitle">IPL and vary off considerations</h4><p>You should be aware
|
||
|
|
of the following IPL and vary off considerations:</p>
|
||
|
|
<ul><li>Recovery of commitment definitions residing on an independent disk pool
|
||
|
|
is performed during the vary on processing of the independent disk pool and
|
||
|
|
is similar to IPL recovery.</li>
|
||
|
|
<li>Commitment definitions in an independent disk pool are not recovered during
|
||
|
|
the system IPL.</li>
|
||
|
|
<li>The vary off of an independent disk pool has the following effects on
|
||
|
|
commitment definitions: <ul><li>Jobs associated with the independent disk pool end.</li>
|
||
|
|
<li>No new commitment definitions are allowed to be created on the independent
|
||
|
|
disk pool.</li>
|
||
|
|
<li>Commitment definitions residing on the independent disk pool become unusable.</li>
|
||
|
|
<li>Commitment definitions residing on the independent disk pool, but not
|
||
|
|
attached to a job, release transaction scoped locks.</li>
|
||
|
|
</ul>
|
||
|
|
</li>
|
||
|
|
</ul>
|
||
|
|
</div>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Remote database considerations</h4><p>You should be aware
|
||
|
|
of the following remote database considerations:</p>
|
||
|
|
<ul><li>You cannot use an LU6.2 SNA connection (protected conversations or Distributed
|
||
|
|
Unit of Work (DUW)) to connect to a remote database from an independent disk
|
||
|
|
pool database. You can use unprotected SNA conversations to connect from an
|
||
|
|
independent disk pool database to a remote database.</li>
|
||
|
|
<li>When commitment control is active for a job or thread, access to data
|
||
|
|
outside the independent disk pool or disk pool group to which the commitment
|
||
|
|
definition belongs is only possible remotely, as if it were data that resides
|
||
|
|
on another system. When you issue an SQL CONNECT statement to connect to the
|
||
|
|
relational database (RDB) on the independent disk pool, the system makes the
|
||
|
|
connection a remote connection.</li>
|
||
|
|
<li>The system disk pool and basic disk pools do not require a remote connection
|
||
|
|
for read-only access to data that resides on an independent disk pool. Likewise,
|
||
|
|
an independent disk pool does not require a remote connection for read-only
|
||
|
|
access to data that resides on the system disk pool or a basic disk pool.</li>
|
||
|
|
</ul>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzakjiasp.htm" title="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.">Commitment control and independent disk pools</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>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|