108 lines
6.1 KiB
HTML
108 lines
6.1 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 names" />
|
||
|
|
<meta name="abstract" content="The system gives names to all commitment definitions that are started for a job." />
|
||
|
|
<meta name="description" content="The system gives names to all commitment definitions that are started for a job." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakjcommitdef.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../books/sc415606.pdf" />
|
||
|
|
<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="rzakjcommitnames" />
|
||
|
|
<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 names</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzakjcommitnames"><a name="rzakjcommitnames"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Commitment definition names</h1>
|
||
|
|
<div><p>The system gives names to all commitment definitions that are started
|
||
|
|
for a job. </p>
|
||
|
|
<p>The following table shows various commitment definitions and their associated
|
||
|
|
names for a particular job.</p>
|
||
|
|
|
||
|
|
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" frame="border" border="1" rules="all"><thead align="left"><tr><th valign="top" id="d0e24">Activation group</th>
|
||
|
|
<th valign="top" id="d0e26">Commit scope</th>
|
||
|
|
<th valign="top" id="d0e28">Commitment definition name</th>
|
||
|
|
</tr>
|
||
|
|
</thead>
|
||
|
|
<tbody><tr><td valign="top" headers="d0e24 ">Any</td>
|
||
|
|
<td valign="top" headers="d0e26 ">Job</td>
|
||
|
|
<td valign="top" headers="d0e28 ">*JOB</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" headers="d0e24 ">Default activation group</td>
|
||
|
|
<td valign="top" headers="d0e26 ">Activation group</td>
|
||
|
|
<td valign="top" headers="d0e28 ">*DFTACTGRP</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" headers="d0e24 ">User-named activation group</td>
|
||
|
|
<td valign="top" headers="d0e26 ">Activation group</td>
|
||
|
|
<td valign="top" headers="d0e28 ">Activation group name (for example, PAYROLL)</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" headers="d0e24 ">System-named activation group</td>
|
||
|
|
<td valign="top" headers="d0e26 ">Activation group</td>
|
||
|
|
<td valign="top" headers="d0e28 ">Activation group number (for example. 0000000145)</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" headers="d0e24 ">None</td>
|
||
|
|
<td valign="top" headers="d0e26 ">Explicitly named</td>
|
||
|
|
<td valign="top" headers="d0e28 ">QDIR001 (example of a system-defined commitment definition for system
|
||
|
|
use only). System-defined commitment definition names begin with <samp class="codeph">Q</samp>.</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" headers="d0e24 ">None</td>
|
||
|
|
<td valign="top" headers="d0e26 ">Transaction</td>
|
||
|
|
<td valign="top" headers="d0e28 ">*TNSOBJ</td>
|
||
|
|
</tr>
|
||
|
|
</tbody>
|
||
|
|
</table>
|
||
|
|
</div>
|
||
|
|
<p>Only IBM<sup>®</sup> Integrated
|
||
|
|
Language Environment<sup>®</sup> (ILE) compiled programs can start commitment control
|
||
|
|
for activation groups other than the default activation group. Therefore,
|
||
|
|
a job can use multiple commitment definitions only if the job is running one
|
||
|
|
or more ILE compiled programs.</p>
|
||
|
|
<p>Original Program Model (OPM) programs run in the default activation group,
|
||
|
|
and by default use the *DFTACTGRP commitment definition. In a mixed OPM and
|
||
|
|
ILE environment, jobs must use the job-level commitment definition if all
|
||
|
|
committable changes made by all programs are to be committed or rolled back
|
||
|
|
together.</p>
|
||
|
|
<p>An opened database file scoped to an activation group can be associated
|
||
|
|
with either an activation-group-level or job-level commitment definition.
|
||
|
|
An opened database file scoped to the job can be associated only with the
|
||
|
|
job-level commitment definition. Therefore, any program, OPM or ILE, which
|
||
|
|
opens a database file under commitment control scoped to the job needs to
|
||
|
|
use the job-level commitment definition.</p>
|
||
|
|
<p>Application programs do not use the commitment definition name to identify
|
||
|
|
a particular commitment definition when making a commitment control request.
|
||
|
|
Commitment definition names are primarily used in messages to identify a particular
|
||
|
|
commitment definition for a job.</p>
|
||
|
|
<p>For activation-group-level commitment definitions, the system determines
|
||
|
|
which commitment definition to use, based on which activation group the requesting
|
||
|
|
program is running in. This is possible because the programs that run within
|
||
|
|
an activation group at any point in time can only use a single commitment
|
||
|
|
definition.</p>
|
||
|
|
<p>For transactions with transaction-scoped locks, the XA APIs and the transaction
|
||
|
|
related attributes added to the CLI determine which commitment definition
|
||
|
|
the invoking thread uses.</p>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <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 class="relinfo"><strong>Related information</strong><br />
|
||
|
|
<div><a href="../books/sc415606.pdf" target="_blank">ILE concepts PDF</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|