73 lines
5.4 KiB
HTML
73 lines
5.4 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 control for batch applications" />
|
|
<meta name="abstract" content="Batch applications might or might not need commitment control. In some cases, a batch application can perform a single function of reading an input file and updating a master file. However, you can use commitment control for this type of application if it is important to start it again after an abnormal end." />
|
|
<meta name="description" content="Batch applications might or might not need commitment control. In some cases, a batch application can perform a single function of reading an input file and updating a master file. However, you can use commitment control for this type of application if it is important to start it again after an abnormal end." />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakjconcepts.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakjnotify.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="../cl/chgqrya.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakjsizetrans.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="rzakjcommitbatch" />
|
|
<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 control for batch applications</title>
|
|
</head>
|
|
<body id="rzakjcommitbatch"><a name="rzakjcommitbatch"><!-- --></a>
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|
<h1 class="topictitle1">Commitment control for batch applications</h1>
|
|
<div><p>Batch applications might or might not need commitment control.
|
|
In some cases, a batch application can perform a single function of reading
|
|
an input file and updating a master file. However, you can use commitment
|
|
control for this type of application if it is important to start it again
|
|
after an abnormal end.</p>
|
|
<p>The input file is an update file with a code in the records to indicate
|
|
that a record was processed. This file and any files updated are placed under
|
|
commitment control. When the code is present in the input file, it represents
|
|
a completed transaction. The program reads through the input file and bypasses
|
|
any records with the completed code. This allows the same program logic to
|
|
be used for normal and starting again conditions.</p>
|
|
<p>If the batch application contains input records dependent on one another
|
|
and contains switches or totals, a notify object can be used to provide information
|
|
about starting again. The values held in the notify object are used to start
|
|
processing again from the last committed transaction within the input file.</p>
|
|
<p>If input records are dependent on one another, they can be processed as
|
|
a transaction. A batch job can lock a maximum of 500 000 000 records. You
|
|
can reduce this limit by using a Query Options File (QAQQINI). Use the QRYOPTLIB
|
|
parameter of the Change Query Attributes (CHGQRYA) command to specify a Query
|
|
Options File for a job to use. Use the COMMITMENT_CONTROL_LOCK_LEVEL value
|
|
in the Query Options File as the lock limit for the job.</p>
|
|
<p>Any commit cycle that exceeds 2000 locks probably slows down system performance
|
|
noticeably. Otherwise, the same locking considerations exist as for interactive
|
|
applications, but the length of time records are locked in a batch application
|
|
might be less important than in interactive applications.</p>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzakjconcepts.htm" title="This topic provides information to help you understand how commitment control works, how it interacts with your system, and how it interacts with other systems in your network.">Commitment control concepts</a></div>
|
|
</div>
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
|
<div><a href="rzakjnotify.htm" title="A notify object is a message queue, data area, or database file that contains information identifying the last successful transaction completed for a particular commitment definition if that commitment definition did not end normally.">Commit notify object</a></div>
|
|
<div><a href="rzakjsizetrans.htm" title="Another way to minimize record locks is to manage the size of the transaction.">Manage transaction size</a></div>
|
|
</div>
|
|
<div class="relref"><strong>Related reference</strong><br />
|
|
<div><a href="../cl/chgqrya.htm">Change Query Attributes (CHGQRYA) command</a></div>
|
|
</div>
|
|
</div>
|
|
</body>
|
|
</html> |