91 lines
5.7 KiB
HTML
91 lines
5.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="Restrictions for commitment control with save-while-active" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaiuswaconsid.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../rzakj/rzakjcommitkickoff.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="rzaiu330" />
|
||
|
|
<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>Restrictions for commitment control with save-while-active</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzaiu330"><a name="rzaiu330"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Restrictions for commitment control with save-while-active</h1>
|
||
|
|
<div><p>Restrictions for commitment control with save-while-active consist of object-level
|
||
|
|
resource restrictions and application programming interface (API) resource
|
||
|
|
restrictions.</p>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaiuswaconsid.htm">Considerations and restrictions for the save-while-active function</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relinfo"><strong>Related information</strong><br />
|
||
|
|
<div><a href="../rzakj/rzakjcommitkickoff.htm">Commitment Control</a></div>
|
||
|
|
</div>
|
||
|
|
</div><div class="nested1" xml:lang="en-us" id="conceptSunDec051606592004"><a name="conceptSunDec051606592004"><!-- --></a><h2 class="topictitle2">Object-level resource restrictions</h2>
|
||
|
|
<div><div class="p">You cannot make object-level resource changes for objects under commitment
|
||
|
|
control that are in the object-level resource library while the server performs
|
||
|
|
checkpoint processing for those objects. You cannot make object-level resource
|
||
|
|
changes if either of the following are true: <ul><li>The commitment definition is at a commitment boundary.</li>
|
||
|
|
<li>Only record-level changes have been made in the uncommitted transaction.</li>
|
||
|
|
</ul>
|
||
|
|
</div>
|
||
|
|
<p>For this situation, the change does not occur until the save-while-active
|
||
|
|
request completes checkpoint processing for the library. After a delay of
|
||
|
|
approximately 60 seconds, you receive inquiry message CPA8351. The inquiry
|
||
|
|
message allows you to continue to wait for the checkpoint processing to complete
|
||
|
|
or to cancel the request for the object-level resource. If the job is a batch
|
||
|
|
job, the QSYSOPR message queue receives inquiry message CPA8351.</p>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div class="nested1" xml:lang="en-us" id="conceptSunDec051607232004"><a name="conceptSunDec051607232004"><!-- --></a><h2 class="topictitle2">Application programming interface (API) resource restrictions</h2>
|
||
|
|
<div><p>You can register an API resource within a commitment control transaction
|
||
|
|
with the QTNADDCR API. If you set the <span class="uicontrol">Allow save while active</span> field
|
||
|
|
to <samp class="codeph">Y</samp> when you use this API, the considerations in this topic
|
||
|
|
do not apply.</p>
|
||
|
|
<div class="p">You cannot place resources under commitment control if the server is performing
|
||
|
|
checkpoint processing for any save-while-active request and either of the
|
||
|
|
following are true: <ul><li>With the Add Commitment Resource API (QTNADDCR program), the commitment
|
||
|
|
definition is at a commitment boundary.</li>
|
||
|
|
<li>Only record-level changes have been made in the uncommitted transaction.</li>
|
||
|
|
</ul>
|
||
|
|
</div>
|
||
|
|
<p>For this situation, the add is delayed until checkpoint processing is complete
|
||
|
|
for the save-while-active request. After a delay of approximately 60 seconds,
|
||
|
|
you receive inquiry message CPA8351. The inquiry message allows you to continue
|
||
|
|
to wait for the checkpoint processing to complete or to cancel the request
|
||
|
|
for the API resource. If the job is a batch job, the QSYSOPR message queue
|
||
|
|
receives the inquiry message CPA8351.</p>
|
||
|
|
<p>If a commitment definition has an API commitment resource associated with
|
||
|
|
it, and checkpoint processing is being performed for any save-while-active
|
||
|
|
request, then the job performing a commit or rollback operation for the commitment
|
||
|
|
definition is delayed immediately after the commit or rollback has been performed.
|
||
|
|
The server delays the job until the completion of checkpoint processing for
|
||
|
|
the save-while-active request. After the checkpoint processing is complete,
|
||
|
|
control is returned back to the job issuing the commit or rollback. This delay
|
||
|
|
is necessary because a commitment definition with an API commitment resource
|
||
|
|
is only considered to be at a commitment boundary <u>immediately after</u> a
|
||
|
|
commit or rollback operation but before control is returned to the user program.
|
||
|
|
Once the commit or rollback operation returns control back to the user program,
|
||
|
|
the commitment definition is no longer considered to be at a commitment boundary.</p>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
|
||
|
|
</body>
|
||
|
|
</html>
|