Force transaction outcomes
Use the administrative console to force the outcomes of transactions. It is recommended that you force a transaction outcome only if a serious problem occurs and you have attempted all other solutions to the problem. For example, a database resource might become locked and does not release. If you frequently must force outcomes, contact IBM WebSphere technical support. For more information, see Get support for WebSphere Application Server for iSeries in the Overview topic.
To intervene in a problematic transaction, perform the following steps in the administrative console:
- Start the administrative console.
- In the topology tree, expand Servers and click Application Servers.
- On the Application Servers page, click the name of the application server that you want to modify.
- On the Configuration tab, click Transaction Service.
- Click the Runtime tab.
- Click Manage Transactions to display the transactions that are currently running on the server.
- Select the check box for the transaction for which you want to force the outcome.
- Click one of the following buttons to cancel the transaction or force an outcome:
- COMMIT
Releases all locks held by a prepared transaction and forces the transaction to commit.- ABORT
Cancels a transaction that is not yet in the prepared state. When you cancel an unprepared transaction, there is no risk to the consistency of the transaction data. This option reverses any completed operations for the transaction.- FINISH
Forces a transaction to finish regardless of whether its outcome has been reported to all participating applications. Normally, a transaction must report its outcome to all participating applications as a requirement of the transaction's successful completion. The FINISH option is useful if one of the participating applications has become permanently unavailable. That application is ignored and the transaction is committed.
Note: Some options might not be available, depending on the status of the transaction.