Re: Journaling, SQL updates/inserts/deletes, and COMMIT(*NONE)

I agree that everyone should be journalling.

I also believe that commitment control is something to be looked into. For
example, if one transaction (like shipping an item) updates multiple files
and part way through the transaction you'd like to back out that
transaction then this is what commitment control is for. For example,
you ship an item.
This transaction updates item master, item master by warehouse, item
master by location, order line file, order header file, GL details, and so
on and your write hits an error on the item master by location because a
write trigger will not allow a negative balance, then you may need to back
out that whole transaction.

But if you're doing journalling so that you can capture every transaction
and can do journal scraping to do analysis then you might be better off to
do IBM i 7.3's "Temporal Tables". It's pretty good. Enough so that we
will be adopting it like crazy as soon as we get a HA solution which
doesn't just milk their maintenance money and starts supporting them.
Sure, you may still be doing journalling but you won't retain your
receivers as long and your analysis will be MUCH easier.


Rob Berendt