53 lines
3.7 KiB
HTML
53 lines
3.7 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="Benefits of using commitment control" />
|
|
<meta name="abstract" content="Recovering a complex application requires detailed application knowledge. Programs cannot be restarted. In this case, commitment control helps solve these problems." />
|
|
<meta name="description" content="Recovering a complex application requires detailed application knowledge. Programs cannot be restarted. In this case, commitment control helps solve these problems." />
|
|
<meta name="DC.Relation" scheme="URI" content="rbaforzahfprg.htm" />
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 1998, 2006" />
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 1998, 2006" />
|
|
<meta name="DC.Format" content="XHTML" />
|
|
<meta name="DC.Identifier" content="rbafoccben" />
|
|
<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>Benefits of using commitment control</title>
|
|
</head>
|
|
<body id="rbafoccben"><a name="rbafoccben"><!-- --></a>
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|
<h1 class="topictitle1">Benefits of using commitment control</h1>
|
|
<div><p>Recovering a complex application requires detailed application
|
|
knowledge. Programs cannot be restarted. In this case, commitment control
|
|
helps solve these problems.</p>
|
|
<p>Sometimes record changes might have to be made with an application program
|
|
or data file utility to reverse the files to just before the last complex
|
|
transaction began. This task becomes more complex if multiple users are accessing
|
|
the files at the same time. In this case, commitment control can help. Commitment
|
|
control locks records from other users during a complex transaction. This
|
|
ensures that other users do not use the records until the transaction is complete.
|
|
At the end of the transaction, the program issues the commit operation, freeing
|
|
the records. However, if the system ends abnormally before performing
|
|
the commit operation, all record changes for that job since the last time
|
|
a commit operation occurred are rolled back. Any affected records that are
|
|
still locked are then unlocked. In other words, database changes roll back
|
|
to a clean transaction boundary.</p>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbaforzahfprg.htm" title="Commitment control lets you define and process a number of changes to database files in a single unit (transaction). It can ensure that complex application transactions are logically synchronized, even if the job or system ends. Two-phase commitment control ensures that committable resources, such as database files on multiple systems, remain synchronized.">Ensure data integrity with commitment control</a></div>
|
|
</div>
|
|
</div>
|
|
</body>
|
|
</html> |