× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Just an FYI. We had a program that would run all day, wake up every 10
minutes and rebuild a file. The programmer was doing it with SQL. Luckily
it was just a work file. However, the commit wasn't being done and the
records were getting removed.

So my thought is to check any jobs like this. While the job is running the
records are there, however, when the job ends and commit wasn't issued,
then they'll disappear.

Our particular issue was a little different. The non committed records
were not getting saved to our backup server. Slowing things down, etc.
Eventually we fixed the program but also excluded this file from backing
up.

On Thu, Sep 13, 2012 at 4:13 PM, Monnier, Gary <Gary.Monnier@xxxxxxxxx>wrote:

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.

--
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.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.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 on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.