RE: OPTIMIZE(*FULL)

Aaron,

Are you seeing the odd results via debug, or when actually running the
program?

If debug, then I think the only correct answer is, don't use *FULL.

If actual results, then I'd open a PMR; or simply not use *FULL ;-)

Charles Wilt
--
iSeries Systems Administrator / Developer
Mitsubishi Electric Automotive America
ph: 513-573-4343
fax: 513-398-1121
  

-----Original Message-----
From: rpg400-l-bounces+cwilt=meaa.mea.com@xxxxxxxxxxxx 
[mailto:rpg400-l-bounces+cwilt=meaa.mea.com@xxxxxxxxxxxx] On 
Behalf Of albartell
Sent: Monday, January 08, 2007 2:54 PM
To: 'RPG programming on the AS400 / iSeries'
Subject: OPTIMIZE(*FULL)

Hi All,
 
I am developing a piece of code that produces odd results when I use
OPTIMIZE(*FULL) on the CRTRPGMOD command.  I am compiling to 
V5R1 on a V5R3
machine.  Take the following as an example of the prototype:
 
 D xyzProc         pr

 D  pParm1                    65535a   varying

 D  pParm2                     1024a   value varying

 D  pParm3                     1024a   value varying 

I invoke the above like so:

D string          s          65535a   varying 
D yyyy            s              4  0 inz(0001) 
 /free

  xyzProc(string: 'yyyy': %editc(yyyy:'X')); 
 
 /end-free


Calling xyzProc when it is compiled with OPTIMIZE(*NONE) or 
OPTIMIZE(*BASIC)
works just fine and all variables have values as expected.  
When I recompile
to OPTIMIZE(*FULL) I get the value of pParm3 in pParm2 (even 
though pParm2
is passed literally!!!!)

Looks like I am not the only one having the problem :-(
http://archive.midrange.com/rpg400-l/200112/msg00617.html
http://archive.midrange.com/rpg400-l/199711/msg00004.html

Anybody have a fix to this problem other than "don't use *FULL"?

Thank,
Aaron Bartell
http://mowyourlawn.com

-- 
This is the RPG programming on the AS400 / iSeries (RPG400-L) 
mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.