eprasad629
New User
Joined: 25 Sep 2009
Posts: 9
Location: Bangalore
|
|
|
|
Hi,
When a job is abended (say after processing 100 records), does DB2 issues a rollback on its own so that all the 100 records are rollbacked?
On situations where both the database and log file (KSDS) are getting updated simultaneously, how to maintain the integrity between file and database?
Please let me know if the question doesn't make sense.
Many thanks for your valuable time. |
|
Kjeld
Active User
Joined: 15 Dec 2009
Posts: 365
Location: Denmark
|
|
|
|
Default action for DB2 connections is to issue a commit if the application terminates normally, and a rollback if the termination is abnormal. And yes, that means that if you have done 100 inserts or updates, all rows are restored to the state they were in when the program started.
If you want to maintain integrity between files and (DB2-) databses in an environment, you have to execute your applications in a DB or DB/DC environment like IMS or CICS. IMS can execute batch programs in BMP or DBB mode.
DB/DC processing is also often called TP environments, transaction processing. Here, 1 transaction is normally defined as 1 logical unit of work, that can be committed or rolled back based on the termination of the transaction. |
|
