76 lines
5.3 KiB
HTML
76 lines
5.3 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="task" />
|
|
<meta name="DC.Title" content="Recover transactions after communications failure" />
|
|
<meta name="abstract" content="You can use instructions in this topic to handle transactions performing work on a remote system after the communication with that system fails." />
|
|
<meta name="description" content="You can use instructions in this topic to handle transactions performing work on a remote system after the communication with that system fails." />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakjtrouble.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakjdspstatus.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakjheuristic.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakjdspstatus.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakjheuristic.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="rzakjrecovtrans" />
|
|
<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>Recover transactions after communications failure</title>
|
|
</head>
|
|
<body id="rzakjrecovtrans"><a name="rzakjrecovtrans"><!-- --></a>
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|
<h1 class="topictitle1">Recover transactions after communications failure</h1>
|
|
<div><p>You can use instructions in this topic to handle transactions performing
|
|
work on a remote system after the communication with that system fails.</p>
|
|
<div class="section">In case of a communications failure, the system typically completes
|
|
the resynchronization with any remote system automatically. However, if the
|
|
failure is catastrophic such that the communications will never be reestablished
|
|
to the remote system (if, for instance, the communication line is cut), you
|
|
must cancel resynchronization and restore transactions yourself. The transactions
|
|
also might be holding locks that need to be released.</div>
|
|
<ol><li class="stepexpand"><span>In iSeries™ Navigator,
|
|
display commitment control information for the transaction with which you
|
|
are working.</span></li>
|
|
<li class="stepexpand"><span>Find the transaction of interest that is trying to resynchronize
|
|
with the remote system. The <span class="uicontrol">Resynchronization in Progress</span> field
|
|
for that transaction is set to <span class="uicontrol">yes</span>.</span></li>
|
|
<li class="stepexpand"><span>Look for transactions that had a connection to the remote system
|
|
by checking the resource Status for individual transactions.</span></li>
|
|
<li class="stepexpand"><span>After identifying transactions, you must force commit or force
|
|
rollback depending on the state of the transaction.</span></li>
|
|
<li class="stepexpand"><span>You can make the decision to commit or rollback after you investigate
|
|
the transaction properties.</span> <ul><li>You can use the <span class="uicontrol">Unit of Work ID</span> to find other parts
|
|
of the transaction on other systems.</li>
|
|
<li>You can also determine to commit or rollback from the state of transaction.
|
|
For example, if a database transaction is performing two-phase commit during
|
|
communication failure and its state after the failure is "prepared" or "last
|
|
agent pending", you might choose to force commit on the transaction.</li>
|
|
</ul>
|
|
</li>
|
|
<li class="stepexpand"><span>After forcing a commit or rollback on the transactions in doubt,
|
|
stop resynchronization on the failed connection for the identified transactions.</span></li>
|
|
</ol>
|
|
</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="reltasks"><strong>Related tasks</strong><br />
|
|
<div><a href="rzakjdspstatus.htm" title="You can use iSeries Navigator to display information about all transactions (logical units of work) on the system. You can also look at information about the job, if any, associated with a transaction.">Display commitment control information</a></div>
|
|
<div><a href="rzakjheuristic.htm" title="You can find when and how to force a rollback or commit, and when to cancel resynchronization in this topic.">When to force commits and rollbacks and when to cancel resynchronization</a></div>
|
|
</div>
|
|
</div>
|
|
</body>
|
|
</html> |