61 lines
3.8 KiB
HTML
61 lines
3.8 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="Transactions" />
|
||
|
|
<meta name="abstract" content="A transaction is a group of changes that appear as a single change, such as the transfer of funds from a savings account to a checking account." />
|
||
|
|
<meta name="description" content="A transaction is a group of changes that appear as a single change, such as the transfer of funds from a savings account to a checking account." />
|
||
|
|
<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="rbafocctrans" />
|
||
|
|
<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>Transactions</title>
|
||
|
|
</head>
|
||
|
|
<body id="rbafocctrans"><a name="rbafocctrans"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Transactions</h1>
|
||
|
|
<div><p>A transaction is a group of changes that appear as a single change,
|
||
|
|
such as the transfer of funds from a savings account to a checking account. </p>
|
||
|
|
<p>Transactions can be classified into the following categories:</p>
|
||
|
|
<div class="p"> <ul><li>Inquiries in which no file changes occur.</li>
|
||
|
|
<li>Simple transactions in which one file is changed each time you press the
|
||
|
|
Enter key.</li>
|
||
|
|
<li>Complex transactions in which two or more files are changed each time
|
||
|
|
you press the Enter key.</li>
|
||
|
|
<li>Complex transactions in which one or more files are changed each time
|
||
|
|
you press the Enter key. These changes represent only part of a logical group
|
||
|
|
of transactions.</li>
|
||
|
|
</ul>
|
||
|
|
</div>
|
||
|
|
<p>Revisions made to files during transaction processing are journaled when
|
||
|
|
using commitment control.</p>
|
||
|
|
<p>If the system or job ends abnormally, journaling alone can ensure that,
|
||
|
|
at most, only the very last record change is lost. However, if the system
|
||
|
|
or job ends abnormally during a complex transaction, the files reflect an
|
||
|
|
incomplete logical transaction. For example, the job might have updated a
|
||
|
|
record in file A, but before it updates a corresponding record in file B,
|
||
|
|
the job ended abnormally. In this case, the logical transaction consists of
|
||
|
|
two updates, but only one update had completed before the job
|
||
|
|
ended abnormally.</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>
|