The TRANSACTION ABORT statement reverts all changes made during the current transaction initiated by a TRANSACTION START statement. All file changes issued during the transaction are undone, returning the data to the state prior to the TRANSACTION START.
To commit the changes made during the current transaction, issue a TRANSACTION COMMIT statement, rather than a TRANSACTION ABORT statement.
Caché MVBasic supports two sets of transaction statements:
UniData-style TRANSACTION START, TRANSACTION COMMIT, and TRANSACTION ABORT.
UniVerse-style BEGIN TRANSACTION, COMMIT, ROLLBACK, and END TRANSACTION.
These two sets of transaction statements should not be combined.
Locks and Transactions
File locks and record locks that were taken out during a transaction are released at the end of a transaction. If there are nested transactions, the release of locks taken out during the inner transactions is delayed until the completion of the outermost transaction. This release of locks is part of a successful TRANSACTION COMMIT or TRANSACTION ABORT operation. Locks are described in the LOCK statement.