RE: Checking for uncommitted changes

[Buck Calabro <mcalabro@xxxxxxxxxxxx>]

On Wednesday, April 22, 1998 12:19 PM, Walden Leverich 
[SMTP:walden@techsoftinc.com] wrote:
> I need a way to look for uncommitted changes in a job.
>
> I have looked into the Retrieve Commitment Information (QTNRCMTI)
> API, but
> this doesn't seem to help me. All I need to know is if there are
> any
> uncommitted changes, I don't care what files they are in or how 
many
> there
> are -- of course I won't complain if I get this info.

-snip-

> Anyone have any good ideas? (Or even any bad ideas)
>
> -Walden

Walden,
  Check out QTNRCMTI again; there *may* be a way out for you.
Commitment Definition Status is set to "L" if there are local,
_closed_ database files with pending changes (among other things.)
It's weak, I know.  I'm assuming that you're suspecting a program
bug that leaves "good" transactions uncommitted.  You've probably
thought of checking the journal receiver or using a trigger to help
locate the offender...

Buck Calabro
Commsoft, Albany, NY
mailto:mcalabro@commsoft.net

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---