A program started via a background input or via CALL Transaction...using... terminates on COMMIT WORK. Statements which were located behind the COMMIT WORK command are no longer called up.
If you call the program directly, and not as described above via CALL Transaction...Using... or via background input, the program is processed correctly.
Via COMMIT WORK, a transaction cannot be taken back and is therefore closed.
For this reason, processing terminates after COMMIT WORK in the background input mode or for CALL Transaction...Using.
Programs which need to edit things after COMMIT WORK consist of several 'Units of Work'. Thus it is not possible to report whether a transaction has successfully run or not.
Ensure that all operations that are essential to the transaction occur before the COMMIT WORK.
No comments:
Post a Comment