Implicit Commitment - DB2 v8

[BrianTyler]

UBD v8 on AIX / RS6000

A Cobol Program updates a database row and then terminates.

Under v7 there was no problem as an implicit commitment took place.

With DB2 v8 the program appears to rollback, and therefore loses the update.

As far as I can see in the documentation, there should be an implicit commit unless a program crashes.

Has anyone else come across this problem and found an explanation / correction; or must we go through every program to make sure that commitments are there?

 

[blom0344]

Brian,

Just a thought. Perhaps the implicit commit in version 7 was deemed something of bug and corrected in version 8?
Unless the application performs an autocommit after each UOW I would expect every piece of code to end with a commit...

T. Blom
Information analyst
tbl@shimano-eu.com

 

[BrianTyler]

Thanks for the comments (by the way what does the T stand for in your name).

Although it is not actually a bug, the concept of Auto-Commit in a non-interactive session has always seemed odd to me.

Obviously, a well-written batch program would have the appropriate commits and roll-backs but we had 'contractors of very little brain' coding out programs.

The IBM documentation says that an auto-commit will take place unless the program seriously crashes, though there is quite a lot of 'small print' to consider.

We have decided to check all programs for Commits, because even if it should work now, who knows what will happen in later releases.

Brian Tyler
Systems Architect

 

[blom0344]

Good occasion to change my signature, I guess

Ties in this case is what I made of my official name (Titus) during high school....

Ties Blom
Information analyst
tbl@shimano-eu.com