Page History
[ 
|../../index.htm#lansa/ugubc_c10060.htm]
You are here:
...
The IBM i operating system provides a facility called "commitment control" that allows programs to define database transaction boundaries.
When a database transaction is in progress, all changes to the database are considered to be "temporary" until the transaction boundary is reached. At the boundary, the program may choose to COMMIT the changes to the database, or ROLLBACK the changes to the last completed transaction boundary (thus removing them from the database).
If the job should end before reaching the transaction boundary, the operating system will automatically ROLLBACK to the last completed transaction boundary, thus removing any incomplete transactions from the database. For interactive jobs, the job begins when the user signs on and finishes with the job ending abnormally, or the user signing off.
It is possible to define and use database files within LANSA that are under IBM i commitment control. However, before doing this you should consider the following points:
...
- Functions with OPTIONS(*PGMCOMMIT).
- SuperServer jobs when Start Commitment Control is set to Y or 1.
- LANSA Open jobs when LceSetCommitmentOn has been called before opening the session.
- LANSA Open for .Net jobs when the Session's CommitmentControlOnServer property is True on connection.
...