You can manage transactions in a PAS for OpenEdge session much the same way that you can manage them in an ABL client session, using transaction blocks and statements that update tables in a database. However, because client and PAS for OpenEdge sessions are entirely separate, including their transaction contexts, the client normally has no direct ability to influence the course of a server transaction that begins and ends within the scope of a single remote procedure request. To allow finer-grained control of transactions running on PAS for OpenEdge, OpenEdge provides an additional transaction type that allows a transaction on a PAS for OpenEdge instance to span multiple client requests.
