95 lines
5.5 KiB
HTML
95 lines
5.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="Example: Jobs and commitment definitions" />
|
||
|
|
<meta name="abstract" content="This figure shows an example of a job that uses multiple commitment definitions." />
|
||
|
|
<meta name="description" content="This figure shows an example of a job that uses multiple commitment definitions." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakjcommitdef.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakjdesc_1.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="rzakjjobs" />
|
||
|
|
<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>Example: Jobs and commitment definitions</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzakjjobs"><a name="rzakjjobs"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Example: Jobs and commitment definitions</h1>
|
||
|
|
<div><p>This figure shows an example of a job that uses multiple commitment
|
||
|
|
definitions.</p>
|
||
|
|
<p> It indicates which file updates are committed or rolled back at each activation
|
||
|
|
group level. The example assumes that all of the updates that are made to
|
||
|
|
the database files by all of the programs are made under commitment control.</p>
|
||
|
|
<br /><img src="rzakj503.gif" alt="Illustration of a job using multiple commitment definitions" /><br /><p>The following table shows how files are committed or rolled back if the
|
||
|
|
scenario in the previous figure changes.</p>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Additional examples of multiple commitment definitions in
|
||
|
|
a job</h4>
|
||
|
|
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" frame="border" border="1" rules="all"><thead align="left"><tr><th rowspan="2" valign="top" id="d0e29">Change in scenario</th>
|
||
|
|
<th colspan="4" valign="top" id="d0e31">Effect on changes to these files:</th>
|
||
|
|
</tr>
|
||
|
|
<tr><th valign="top" id="d0e34">F1 and F2</th>
|
||
|
|
<th valign="top" id="d0e36">F3 and F4</th>
|
||
|
|
<th valign="top" id="d0e38">F5 and F6</th>
|
||
|
|
<th valign="top" id="d0e40">F7</th>
|
||
|
|
</tr>
|
||
|
|
</thead>
|
||
|
|
<tbody><tr><td valign="top" headers="d0e29 ">PGMX performs a rollback operation instead of a commit operation (3=
|
||
|
|
=COMMIT becomes ROLLBACK).</td>
|
||
|
|
<td valign="top" headers="d0e31 d0e34 ">Still pending</td>
|
||
|
|
<td valign="top" headers="d0e31 d0e36 ">Rolled back</td>
|
||
|
|
<td valign="top" headers="d0e31 d0e38 ">Already committed</td>
|
||
|
|
<td valign="top" headers="d0e31 d0e40 ">Rolled back</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" headers="d0e29 ">PGMZ performs a commit operation before returning to PGMX.</td>
|
||
|
|
<td valign="top" headers="d0e31 d0e34 ">Still pending</td>
|
||
|
|
<td valign="top" headers="d0e31 d0e36 ">Committed by PGMZ</td>
|
||
|
|
<td valign="top" headers="d0e31 d0e38 ">Already committed</td>
|
||
|
|
<td valign="top" headers="d0e31 d0e40 ">Committed</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" headers="d0e29 ">PGMZ attempts to start commitment control specifying <samp class="codeph">CMTSCOPE(*ACTGRP)</samp>
|
||
|
|
after updating file F7. The attempt fails because changes are pending using
|
||
|
|
the job-level commitment definition.</td>
|
||
|
|
<td valign="top" headers="d0e31 d0e34 ">Still pending</td>
|
||
|
|
<td valign="top" headers="d0e31 d0e36 ">Still pending</td>
|
||
|
|
<td valign="top" headers="d0e31 d0e38 ">Already committed</td>
|
||
|
|
<td valign="top" headers="d0e31 d0e40 ">Still pending</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" headers="d0e29 ">PGMX does not start commitment control and does not open files F3 and
|
||
|
|
F4 with COMMIT(*YES). PGMZ attempts to open file F7 with COMMIT(*YES).</td>
|
||
|
|
<td valign="top" headers="d0e31 d0e34 ">Still pending</td>
|
||
|
|
<td valign="top" headers="d0e31 d0e36 ">Not under commitment control</td>
|
||
|
|
<td valign="top" headers="d0e31 d0e38 ">Already committed</td>
|
||
|
|
<td valign="top" headers="d0e31 d0e40 ">File F7 cannot be opened because no *JOB commitment definition exists
|
||
|
|
(PGMX did not create it).</td>
|
||
|
|
</tr>
|
||
|
|
</tbody>
|
||
|
|
</table>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<ul class="ullinks">
|
||
|
|
<li class="ulchildlink"><strong><a href="rzakjdesc_1.htm">Image description</a></strong><br />
|
||
|
|
This image illustrates how a job can use multiple commitment definitions.</li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<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>
|
||
|
|
</body>
|
||
|
|
</html>
|