Conversion to RPGLE & commitment control

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.

Some of the issues are:
-       The RPG programs need to be converted to RPGLE so commit can span
all the programs.  Will a simple IBM conversion {no commit} change how the
program works?  Does IBM guarantee there is no difference?
-       Will the performance with commit suffer?
-       What is needed to add in commit to this process?
-       Some programs don't do any updates.  They just return info.  Do they
need to be converted to RPGLE?
-       Any others?


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?"


Vincent Forbes
CIBC
Toronto, Ontario

Nothing is impossible...if you don't have to do it yourself.