Re: Conditional Processing with NoPass Parameters

[Barbara Morris <bmorris@xxxxxxxxxx>]

jrc@xxxxxxxxxx wrote:
> 
> ...
> I use this approach all the time to establish
> default behaviours: add the 'Value' attribute to
> the prototype for the new parm:
> 
> D CalcDat         pr
> ExtPgm('CALCDAT')
> ...
> D  outDat                       10
> 
> D  outDatFmt                    10
> Value Options(*nopass)
> 
> 
> Now you can use outDatFmt even if it wasn't
> sent... just don't forget to initlize it...
> 

Joel, that's a dangerous thing to do.  You're assuming that there is
storage available for your procedure to use, but that's not necessarily
the case.

Since the system doesn't know you're using that storage as a local
variable, that storage could get used for parameter passing when your
procedure makes a call.  (Your procedure might make explicit calls, or
the compiler might generate some calls to the RPG runtime.)

Even if this is working for you now, it might stop working at any time.