72 lines
5.1 KiB
HTML
72 lines
5.1 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="Commit cycle identifier" />
|
||
|
|
<meta name="abstract" content="A commit cycle is the time from one commitment boundary to the next. The system assigns a commit cycle identifier to associate all of the journal entries for a particular commit cycle together. Each journal that participates in a transaction has its own commit cycle and its own commit cycle identifier." />
|
||
|
|
<meta name="description" content="A commit cycle is the time from one commitment boundary to the next. The system assigns a commit cycle identifier to associate all of the journal entries for a particular commit cycle together. Each journal that participates in a transaction has its own commit cycle and its own commit cycle identifier." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakjresources.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="rzakjcycle" />
|
||
|
|
<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>Commit cycle identifier</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzakjcycle"><a name="rzakjcycle"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Commit cycle identifier</h1>
|
||
|
|
<div><p>A <dfn class="term">commit cycle</dfn> is the time from one commitment boundary
|
||
|
|
to the next. The system assigns a <dfn class="term">commit cycle identifier</dfn> to
|
||
|
|
associate all of the journal entries for a particular commit cycle together.
|
||
|
|
Each journal that participates in a transaction has its own commit cycle and
|
||
|
|
its own commit cycle identifier.</p>
|
||
|
|
<p>The commit cycle identifier is the journal sequence number of the C SC
|
||
|
|
journal entry written for the commit cycle. The commit cycle identifier is
|
||
|
|
placed in each journal entry written during the commit cycle. If more than
|
||
|
|
one journal is used during the commit cycle, the commit cycle identifier for
|
||
|
|
each journal is different.</p>
|
||
|
|
<p>You can specify that the fixed-length portion of the journal entry includes
|
||
|
|
transaction information by specifying the Logical Unit of Work (*LUW) value
|
||
|
|
for the Fixed-Length Data (FIXLENDTA) parameter of the Create Journal (CRTJRN)
|
||
|
|
or Change Journal (CHGJRN) command. By specifying the FIXLENDTA (*LUW) parameter,
|
||
|
|
the fixed-length portion of each C SC journal entry will contain the Logical
|
||
|
|
Unit of Work ID (LUWID) of the current transaction. Likewise for XA transactions,
|
||
|
|
if you specify the FIXLENDTA (*XID) parameter, the fixed-length portion of
|
||
|
|
each C SC journal entry will contain the XID of the current transaction. The
|
||
|
|
LUWID or XID can help you find all the commit cycles for a particular transaction
|
||
|
|
if multiple journals or systems are involved in the transaction.</p>
|
||
|
|
<p>You can use the Send Journal Entry (QJOSJRNE) API to write journal entries
|
||
|
|
for API resources. You have the option of including the commit cycle identifier
|
||
|
|
on those journal entries.</p>
|
||
|
|
<p>You can use the commit cycle identifier to apply or remove journaled changes
|
||
|
|
to a commitment boundary using the Apply Journaled Changes (APYJRNCHG) command
|
||
|
|
or the Remove Journaled Changes (RMVJRNCHG) command. These limitations apply:</p>
|
||
|
|
<ul><li>Most object-level changes made under commitment control are written to
|
||
|
|
the journal but are not applied or removed using the APYJRNCHG and RMVJRNCHG
|
||
|
|
commands.</li>
|
||
|
|
<li>The QJOSJRNE API writes user-created journal entries with a journal code
|
||
|
|
of <samp class="codeph">U</samp>. These entries cannot be applied or removed using the
|
||
|
|
APYJRNCHG and RMVJRNCHG commands. They must be applied or removed with a user-written
|
||
|
|
program.</li>
|
||
|
|
</ul>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzakjresources.htm" title="When you place an object under commitment control, it becomes a committable resource. It is registered with the commitment definition. It participates in each commit operation and rollback operation that occurs for that commitment definition.">How commitment control works with objects</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|