When long transactions are in effect, the client application is responsible for controlling when the transaction ends (by issuing either a commit or a rollback).
If the DB2 access service encounters a begin transaction phrase in a request, the phrase is ignored because the phrase does not affect the unit of work management.
The client application issues a commit or rollback statement for each transaction. When the client application closes its connection, the DB2 access service issues a rollback before exiting. Therefore, the client must commit any work that should be committed.
If the client application does not issue timely commits or rollbacks, then host resources, such as the APPC session or DB2 logging and locking, are held for an indeterminate amount of time. Therefore, long transactions can cause performance problems for other applications that need to access the same resource.
See the Managing processing section that follows for more information about the Allocate and StopCondition properties, and how they interact with the transaction mode.
| Copyright © 2005. Sybase Inc. All rights reserved. |
|
|
