MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » September 2012

RE: Tracing Physicial File R/W Actions



fixed

Ah, there's the rub.

If the batch program is running under commitment control and ends without committing the database changes those changes are lost. It is no different than a PC client not committing entries.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Musselman, Paul
Sent: Thursday, September 13, 2012 1:02 PM
To: Midrange Systems Technical Discussion
Subject: RE: Tracing Physicial File R/W Actions

Does that hold true for batch jobs? Or does a batch job 'assume' a commit if the job ends normally??

Paul E Musselman
PaulMmn@xxxxxxxxxxxxxxxxxxxx

Rob said (in part):
Yes, check the journals and journal receivers. One question, are they forgetting to COMMIT transactions? I once wrote a program that forgot that. Hey, data's there! Sign off, data's gone!? Didn't commit, so it did a rollback.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.






Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2014 by MIDRANGE dot COM and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available here. If you have questions about this, please contact