RE: Subprocedures: *OMIT vs. *NOPASS

I agree with Paul, with one addition...   I also use *NOPASS when I want
to keep a procedure backwards-compatable.  I.e., if I add a parameter to
a procedure in an existing service program, I add it onto the end and use
*NOPASS.   That way, the old programs using this procedure don't need to
be changed.


On Wed, 13 Mar 2002, Nicolay, Paul wrote:
>
> *OMIT is targeted for parameters in the middle of the list, while *NOPASS at
> the end of the list.  Personally I only use *NOPASS, and put optional
> parameters at the end as they're usually less important.  This also makes
> calling the procedure more transparent.
>
> Kind regards,
> Paul
>
> -----Original Message-----
> From: Bartell, Aaron L. (TC) [mailto:ALBartell@taylorcorp.com]
> Sent: 13 March, 2002 16:37
> To: 'rpg400-l@midrange.com'
> Subject: Subprocedures: *OMIT vs. *NOPASS
>
> A co-worker and I are trying to decide which one of these we should use when
> passing data to a subprocedure.  Could I get some opinions on when you feel
> each should be used?
>
> Thanks,
> Aaron Bartell