ibm-information-center/dist/eclipse/plugins/i5OS.ic.rzakj_5.4.0.1/rzakjcancel.htm

84 lines
5.3 KiB
HTML
Raw Normal View History

2024-04-02 14:02:31 +00:00
<?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="End a long-running rollback" />
<meta name="abstract" content="You can find how to end long-running rollbacks that consume critical processor time, lock resources, or take up storage space in this topic." />
<meta name="description" content="You can find how to end long-running rollbacks that consume critical processor time, lock resources, or take up storage space in this topic." />
<meta name="DC.Relation" scheme="URI" content="rzakjtrouble.htm" />
<meta name="DC.Relation" scheme="URI" content="../cl/crtdtaara.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="rzakjcancel" />
<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>End a long-running rollback</title>
</head>
<body id="rzakjcancel"><a name="rzakjcancel"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">End a long-running rollback</h1>
<div><p>You can find how to end long-running rollbacks that consume critical
processor time, lock resources, or take up storage space in this topic.</p>
<p>A rollback operation removes all changes made within a transaction since
the previous commit operation or rollback operation. During a rollback operation,
the system also releases locks related to the transaction. If the system contains
thousands of transactions, the system can take hours to complete a rollback
operation. These long-running rollbacks can consume critical processor time,
lock resources or take up storage space.</p>
<p>Before you end a long-running rollback, you need to know which commitment
definitions are being rolled back and what state the commitment definitions
are in. The State field for commitment definitions that are rolling back is
set to ROLLBACK IN PROGRESS.</p>
<p>Use the Work with Commitment Definitions (WRKCMTDFN) command to check the
status of a rollback by following these steps:</p>
<ol><li>Type WRKCMTDFN JOB(*ALL) from the character-based interface.</li>
<li>Type F11 to display the State field.</li>
</ol>
<p>If you end a long-running rollback, files that were changed during the
transaction will be left with partial transactions. You must not end a rollback
if your files cannot have partial transactions. To see which files were changed
during the transaction, choose option 5 to display status from the WRKCMTDFN
list. Press F6 to display resource status and select Record Level.</p>
<p>You must have All Object (*ALLOBJ) special authority to end a long-running
rollback. To end a long-running rollback, follow these steps:</p>
<ol><li>Type WRKCMTDFN JOB(*ALL) from the character-based interface.</li>
<li>Type option 20 (End rollback) on the commitment definition you want to
end.</li>
</ol>
<p>Files with partial transactions have the Partial Transactions Exist, Rollback
Ended field set to *YES in the output from the Display File Description (DSPFD)
command. You must remove partial transactions before the file can be used.
You can remove partial transactions by deleting the file and restoring the
file from a prior save. If you do not have a prior save, you can use the Change
Journaled Object (CHGJRNOBJ) command to reset the Partial Transaction Exists
state so that you can open the file. Using the CHGJRNOBJ requires you to edit
the file to bring the file to a consistent state. You must use the CHGJRNOBJ
command only if no prior save is available.</p>
<div class="section" xml:lang="en-us" id="rzakjcancel__disable"><a name="rzakjcancel__disable"><!-- --></a><h4 class="sectiontitle">Disable the ability to end a
long-running rollback</h4><p>Users with *ALLOBJ special authority can end
rollbacks by default. If you want to restrict users who have *ALLOBJ special
authority from ending rollbacks, you can do this by creating data area QGPL/QTNNOENDRB.</p>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzakjtrouble.htm" title="You can read this information when you need to troubleshoot commitment control.">Troubleshoot transactions and commitment control</a></div>
</div>
<div class="relref"><strong>Related reference</strong><br />
<div><a href="../cl/crtdtaara.htm">Create Data Area (CRTDTAARA) command</a></div>
</div>
</div>
</body>
</html>