A user-defined transaction is a unit of work explicitly defined by the client application with transaction control statements such as begin tran, commit, and rollback. A unit of work is the data that the users want to confirm was added to the back-end database.
The parse exit routine is called once for each SQL statement, including the transaction control statements that define the transaction. Your routine should not alter transaction control statements.
WARNING! A customer-defined transaction causes AMD2 to maintain database locks and the DirectConnect server-to-mainframe connection until you end the transaction. If your parse exit routine alters the transaction control statements, especially those that explicitly end the transaction, your routine can impact DB2 UDB and other mainframe resource usage.
