Re: %ADDR and possible pointer problems

[Jon Paris <jon.paris@xxxxxxxxxxxxxx>]

Have you checked PTFs? I have this vague memory of a parameter passing problem with V6.

I'm assuming your prototype matches the PI and that you have actually passed 3 parameters as you state. You haven't shown us your code that checks for the optional third parm and referencing it when it wasn't passed could cause this kind of error.

As you note, you should really be passing the parm normally (i.e. by reference) and using LikeDS to define the parm. There's absolutely no benefit to doing it the way you have and there's lots of opportunity to screw up.


On Mar 6, 2012, at 6:57 AM, rpg400-l-request@xxxxxxxxxxxx wrote:

> Since we installed Version of the RPG compiler with the attribute o/s current we have been encountering problems with a technique that previously worked ok.
> <snip>
>
>                  wrkCRtn = cpReadI( XmoYAccVal : XmoCValeur
>
>                                                :  %addr(vlxopc)  )     
>
> In the called function we do the following 
>
>
> PcpRead           B                   Export                 
>
> d                 Pi                  Like( Tint )           
>
> d ii_YAcc                        1    Value                  
>
> d ii_CVal                       12    Value                  
>
> d PtrVlXOpc                           Like( TPointer ) Value 
>
> d                                     Options( *NoPass )     
>
>
> d vlxopc        e ds                  extname(dvlxopc)    
>
> d                                     Based(PtrVlxOpc)     

Jon Paris

www.partner400.com
www.SystemiDeveloper.com