When an OpenEdge database is configured as a resource manager for distributed JTA transactions, the transaction manager is responsible for establishing and maintaining the state of the transaction. The database receives an identifier for the global transaction. Multiple threads of execution process the transaction and have the following effects:
Records can be locked by a JTA transaction with no user associated with the lock.
Record locks can exist at database startup.
Locks are owned by the transaction and not the user.
Records can be locked by a JTA transaction with no user associated with the lock.