RE: Conversion to RPGLE & commitment control

Vincent,

I know of no reason why the RPG III must be converted to RPG IV for the
commit to span all programs.  Where did you hear this from?  The
commitment control boundary can actually be outside of the RPG program
(using STRCMTCTL and ENDCMTCTL CL commands) there it doesn't make sense
to me that it would matter if one RPG program is called or 9.

I'm pretty sure IBM doesn't officially guarantee anything when it comes
to software, let alone the CVTRPGSRC command.  However, I think you'll
find that most consider it 99.999% reliable.  The only time I've seen
problems is when something was wrong in the RPG III program and while it
didn't seem to affect the RPG III program, it caused a problem with the
converted RPG IV.  For example, mismatches in parameters when calling
programs.

To use Commitment control, your files must be journaled, you can issue a
STRCMTCTL command in CL before starting the RPG program, the RPG program
must open the file under commitment control (f-spec has COMMIT in either
continuation line pos 54-59 [RPG III] or keyword [RPG IV], somewhere you
must issue commit/rollback, use the ENDCMTCTL afterward.

If you already have your files journaled, then using commitment control
can actually _INCREASE_ performance.  In other words, commitment control
itself has little impact.  Journaling your files has an impact.  You
might want to check out the REDBOOK "Striving for Optimal Journal
Performance on DB2 Universal Database for iSeries".

HTH,


Charles Wilt
--
iSeries Systems Administrator / Developer
Mitsubishi Electric Automotive America
ph: 513-573-4343
fax: 513-398-1121
 
-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Forbes, Vincent
Sent: Friday, November 04, 2005 11:24 AM
To: RPG programming on the AS400 / iSeries
Subject: 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.