Transaction Boundaries |
DEVELOPER |
 |
If a Task is executed where commits have been suppressed via ENABLE(&#@SUPP-COMM) (or ENABLE(&@#NOAUTOC) in the S/390 product), all pending transactions will not be committed to the database upon termination of the Task session: they will be rolled-back instead. Usually the session termination is coincident with the termination of the Task, but it is not true in one case discussed in Logon Link to Function as a Task. In this case, a transaction boundary started in the logon link to task will continue into the incoming request’s Task functions. On termination of the requested Task, all pending transactions will be rolled back.
Topic ID: 540164