RE: Question on Commit/Rollback

["Glenn Birnbaum" <gbirnba@xxxxxxx>]

Yes Marvin - 

If a job ends (for any reason, a failure or just signoff) before a
COMMIT is issued, the files under commitment control will rollback.  

We've discovered this occasionally with our replication systems when an
open commit is left in a job all day.  We see the apply point back at
the time the open commit began and it isn't until the job ends that our
replication system 'catches up', even though it really wasn't behind.
It was just waiting for the commit before it would apply the DB changes.

Glenn

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Marvin Radding
Sent: Tuesday, June 27, 2006 4:14 PM
To: midrange-l@xxxxxxxxxxxx
Subject: Question on Commit/Rollback

We are having a problem here with commit/rollback.

In a program with several files under commitment control, the problem
occurs when the program aborts. Can anyone tell me what happens if the
commit or rollback commands are not issued prior to signing off?  I
haven't much experience with this kind of thing and my inquiring minds
wants to know.

Right now the procedure is to examine the database and manually delete
the records that were not committed. but this strikes me as strange.
Doesn't the system automatically rollback when you signoff if you
haven't committed?

Marvin