Fellow midrangers with more knowledge here will need to answer your
questions. I only know that, when we have run SQL scripts to insert
records in tables that were journaled, they would be lost at the end of the
job if no COMMIT was performed.

- Dan

On Thu, Aug 20, 2015 at 1:35 PM, Glenn Gundermann <
glenn.gundermann@xxxxxxxxx> wrote:

Hi Dan,

Mmmmm. Commitment control is used in programs that update the master files
in the ERP package we use.

More details in my scenario:

We have an Item Masterfile table. I have an 'after insert' and 'after
update' trigger on it. The trigger program writes minimal data to fileA
and sends a 'Y' to a data queue to wake up a never ending program (code in
original email), which then retrieves more information and does various
calculations and writes to fileB.

If the ERP program does changes to the Item Masterfile and then does a
a. Will I see records in the journal to the Item Masterfile to that effect?
b. Will the initial changes cause the trigger to fire and cause records to
be written to fileA?

Yours truly,

Glenn Gundermann

This thread ...


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

This mailing list archive is Copyright 1997-2020 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].