I'm not sure if our experience is relevant or not...
We have very few applications that use committment control. We had
an issue with an application losing transactions. The clerks swore
up and down that they had entered batches of transactions that
'disappeared.'
What was happening was the interactive session was running under
committment control. And the user was 'signing off' by powering off
their monitor.
When our backups ran, the file(s) couldn't be saved because there was
an open committment pending. And our operator cancelled the
interactive job, gave the backup a retry, and all was good.
And then the user complained about disappering transactions again.
Yep. Cancelling the interactive job rolled back all of those
transactions!
--Paul E Musselman
This mailing list archive is Copyright 1997-2025 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.
midrange.com
