85 lines
6.2 KiB
HTML
85 lines
6.2 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 definition" />
|
||
|
|
<meta name="abstract" content="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." />
|
||
|
|
<meta name="description" content="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." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakjconcepts.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakjscope.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakjcommitnames.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakjjobs.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakjcommitops.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakjiasp.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakjconsidcdef.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="rzakjcommitdef" />
|
||
|
|
<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 definition</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzakjcommitdef"><a name="rzakjcommitdef"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Commitment definition</h1>
|
||
|
|
<div><p>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.</p>
|
||
|
|
<p> The commitment definition contains information that pertains to the resources
|
||
|
|
that are being changed under commitment control within that job. The system
|
||
|
|
maintains the commitment control information in the commitment definition
|
||
|
|
as the commitment resources change, until the commitment definition is ended.
|
||
|
|
Each active transaction on the system is represented by a commitment definition.
|
||
|
|
A subsequent transaction can reuse a commitment definition after each commit
|
||
|
|
or rollback of an active transaction.</p>
|
||
|
|
<p>A commitment definition generally includes:</p>
|
||
|
|
<ul><li>The parameters on the STRCMTCTL command.</li>
|
||
|
|
<li>The current status of the commitment definition.</li>
|
||
|
|
<li>Information about database files and other committable resources that
|
||
|
|
contain changes that are made during the current transaction.</li>
|
||
|
|
</ul>
|
||
|
|
<p>For commitment definitions with job-scoped locks, only the job that starts
|
||
|
|
commitment control knows that commitment definition. No other job knows that
|
||
|
|
commitment definition.</p>
|
||
|
|
<p>Programs can start and use multiple commitment definitions. Each commitment
|
||
|
|
definition for a job identifies a separate transaction that has committable
|
||
|
|
resources associated with it. These transactions can be committed or rolled
|
||
|
|
back independently from transactions that are associated with other commitment
|
||
|
|
definitions that are started for the job.</p>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<ul class="ullinks">
|
||
|
|
<li class="ulchildlink"><strong><a href="rzakjscope.htm">Scope for a commitment definition</a></strong><br />
|
||
|
|
The <em>scope</em> of a commitment definition determines which programs
|
||
|
|
will use that commitment definition, and how locks acquired during transactions
|
||
|
|
are scoped. </li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzakjcommitnames.htm">Commitment definition names</a></strong><br />
|
||
|
|
The system gives names to all commitment definitions that are started for a job.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzakjjobs.htm">Example: Jobs and commitment definitions</a></strong><br />
|
||
|
|
This figure shows an example of a job that uses multiple commitment definitions.</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="rzakjcommitops.htm" title="A commit operation makes permanent all changes made under commitment control since the previous commit or rollback operation. The system also releases all locks related to the transaction.">Commit operation</a></div>
|
||
|
|
<div><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><a href="rzakjconsidcdef.htm" title="You must be aware of the considerations for commitment definitions in this topic when you use independent disk pools.">Independent disk pool considerations for commitment definitions</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|