|
rpg400-l-request@xxxxxxxxxxxx wrote: > 1. Conversion to RPGLE & commitment control (Forbes, Vincent) > >In our application, we have a series of 9 RPG programs that creates all >transactions. The problem is that there is little or no error checking for >such things as record lock. We have nightly audit reports that verify >balances & every few months or so it finds a problem where not all of the >files were updated. > >I am trying to make a case to put commitment control on this process. <snip> >Since I work for a bank, the paranoia level is high. The general feeling is >"If it ain't broke...don't fix it" and "Do you realize how much testing we >will have to do for this change?" Ummm... your employer is a _bank_ and you're not already using commitment control? Canadian Imperial Bank of Commerce? Wow. May we assume that you _are_ at least journalling? Tom Liotta
As an Amazon Associate we earn from qualifying purchases.
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.