Your Browser is not longer supported

Please use Google Chrome, Mozilla Firefox or Microsoft Edge to view the page correctly
Loading...

{{viewport.spaceProperty.prod}}

Stopping the execution of transactions (STOP)

&pagelevel(4)&pagelevel

STOP {transaction-id | NEW | ALL}          

The STOP command stops the execution of one or more transactions, depending on the operand specified. It places the designated transactions in the STOP state.

The STOP state of a transaction can be canceled by one of the following events:

  • GO command

  • CANCEL command for the transaction

  • CLOSE command

  • PERFORM command

transaction-id


Identifier for a current transaction;
stops the specified transaction

NEW

Allows new transactions, but does not start them

ALL

Stops all currently known transactions; also admits new ones, but does not start them

A transaction is not stopped until it issues a DML statement. If the DBH is currently processing a DML statement of the transaction, the statement is processed to completion; the transaction is not stopped until it issues the next DML statement.

To prevent global deadlocks, new transactions from UTM applications and in secondary subtransactions are rejected with status codes.