Re: CRTRPGMOD

[Scott Klement <rpg400-l@xxxxxxxxxxxxxxxx>]

Hello,

I agree with Chamara's interpretation of what the help file said. 
Basically, to make the code as fast as possible, the optimizer takes 
"short cuts" that sometimes cause the debugger to provide incorrect 
information.

However, my experience is that optimizing makes programs harder to 
support while providing *no* noticeable performance gain.

Here's my suggestion:  Write your programs and compile them normally. 
Then, check to see if they perform adequately.  If they do, great...  if 
not, then try optimize(*full) and see if it makes any noticeable 
difference.  If it does, great!

But I've been coding in RPG IV for 13 years now, and have run into many 
situations where performance was unacceptable.  But never in all those 
times, did OPTIMIZE(*FULL) solve the problem.  In all cases, I had to 
find a more efficient way of reading a file, or a more efficient 
algorithm in my code. It makes little sense to give up serviceability 
for a 0.001% performance gain. YMMV.


Chamara Withanachchi wrote:
> OPTIMIZE(*FULL) generates the most efficient code -- and the compile
> process also takes longer. The program should run faster than with
> either of the other two options. The debugger will let you see (but
> not change) field values; but the debugger may not show you the
> correct current field values.