Fw: Change commitment control after compilation

@OT youn or old: I'm old enough (62) to do things as I want and not to do things I ' don't wanna do...

@Buck: so the discussion is opened:

<Buck>
But does this add any business functionality? It
seems to me that a COMMIT cycle that holds exactly one master row is
meaningless. Isn't a 'normal' COMMIT cycle a master row and some rows
in child tables?
</Buck>

No, I don't think so! you've taken the first barrier, your progarmms are compiled with commit, your files are journaled and nothing evildid happen - and maybe you've got a benefit: your tables are journaled. And if you would normalize your tables, a single table might be split in two (or more) and you would take the corrrespondet updates in one transaction, and it' done.

<Buck>
But how would we correct the error and re-process the undone
transaction?
</Buck>

The report could be produced as today and the customer would not see any difference. The diffrence to you (behind the curtain) would be: no data to repair, but the transaction would to be restarted again. Maybe your batch process is designed to process all unprocessed records, the next run will to this anyway (one example, I'm thinking of, we did speed up processes by parallelisation and some transactions died, caused by lock conflicts and simply making three retries did solve this all. In other cases a transaction dies, because a needed information was missing (the sales information arrived before the article information), this could not work this night, but maybe next.

<Buck>
When a ROLLBACK happens, subtract out
the 'details' from the total?
</Buck>

I would increment/decremet within the corresponding transaction and so the rollback would do it's work. In some important scenarios, we did some redundandent work, summing up what came in and showing the diffrence to what we could bring consistent to the database.

The most important goal of all this is: get rid of the effort to cleanup "the mess" happeneing by applications without transaction safety. Here you will get the time for redesign activities - it's the only chance!!!

<Buck>
You might be pleasantly surprised at how many of us have
journalling turned on even if commitment control isn't retrofitted to
every program.
</Buck>

That's good news, primarly for you - and a liitle bit for me.
BTW; I have a little tool to format journal entries (generating a table with the record layout of the journal image, adding the most important joural data) and i recognized, that I didn't publish it at my open source site - I should change this. Be patient, at the moment I'm busy with my CommandGate activities, and sometimes I have to work for money...

Dieter

PS: did we meet together at Vienna in the Hotel Bar???