66 lines
5.2 KiB
HTML
66 lines
5.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="Scenarios and examples: Commitment control" />
|
||
|
|
<meta name="abstract" content="You can read scenarios and examples in this topic to see how one company sets up commitment control. Read code examples for programs that use commitment control." />
|
||
|
|
<meta name="description" content="You can read scenarios and examples in this topic to see how one company sets up commitment control. Read code examples for programs that use commitment control." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakjcommitkickoff.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakjcommitscenario.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakjpracticecommit.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakjloggingfile.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakjusenotify.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakjproccprog.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="rzakjscenario" />
|
||
|
|
<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>Scenarios and examples: Commitment control</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzakjscenario"><a name="rzakjscenario"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Scenarios and examples: Commitment control</h1>
|
||
|
|
<div><p>You can read scenarios and examples in this topic to see how one
|
||
|
|
company sets up commitment control. Read code examples for programs that use
|
||
|
|
commitment control.</p>
|
||
|
|
<p>The following scenario shows how the JKL toy company implements
|
||
|
|
commitment control to track transactions on its local database.</p>
|
||
|
|
<p>The following examples provide sample code for commitment control. The
|
||
|
|
practice problem is an RPG program that implements commitment control. It
|
||
|
|
includes a logic flow that shows what is happening each step of the way.</p>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<ul class="ullinks">
|
||
|
|
<li class="ulchildlink"><strong><a href="rzakjcommitscenario.htm">Scenario: Commitment control</a></strong><br />
|
||
|
|
The JKL Toy Company uses commitment control to protect the database records for manufacturing and inventory. This scenario shows how JKL toy company uses commitment control to transfer a part from its inventory department to its manufacturing department.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzakjpracticecommit.htm">Practice problem for commitment control</a></strong><br />
|
||
|
|
This practice problem assists you in understanding commitment control
|
||
|
|
and its requirements. These steps assume that you are familiar with the i5/OS™ licensed
|
||
|
|
program, the data file utility (DFU), and this topic collection.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzakjloggingfile.htm">Example: Use a transaction logging file to start an application</a></strong><br />
|
||
|
|
This example provides sample code and instructions of how to use a transaction logging file to start an application after an abnormal end.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzakjusenotify.htm">Example: Use a notify object to start an application</a></strong><br />
|
||
|
|
When a program is started after an abnormal end, it can look for an entry in the notify object. If the entry exists, the program can start a transaction again. After the transaction has been started again, the notify object is cleared by the program to prevent it from starting the same transaction yet another time.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzakjproccprog.htm">Example: Use a standard processing program to start an application</a></strong><br />
|
||
|
|
A standard processing program is one way to start your application again using one database file as the notify object for all applications. This approach assumes that user profile names are unique by user for all applications using the standard program.</li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzakjcommitkickoff.htm" title="Commitment control is a function that ensures data integrity. It allows you to define and process a group of changes to resources, such as database files or tables, as a transaction.">Commitment control</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|