RE: Optional Parameters in Subproceedures -- RPG400-L

Subject: RE: Optional Parameters in Subproceedures
From: Scott Mildenberger <Smildenber@xxxxxxxxxxxx>
Date: Mon, 18 Feb 2002 14:15:38 -0700
List-archive: <http://archive.midrange.com/rpg400-l/>
List-help: <mailto:rpg400-l-request@midrange.com?subject=help>
List-id: RPG programming on the AS400 / iSeries <rpg400-l.midrange.com>
List-post: <mailto:rpg400-l@midrange.com>
List-subscribe: <http://lists.midrange.com/cgi-bin/listinfo/rpg400-l>,<mailto:rpg400-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/cgi-bin/listinfo/rpg400-l>,<mailto:rpg400-l-request@midrange.com?subject=unsubscribe>

Check %parms

> -----Original Message-----
> From: Wills, Mike N. (TC) [mailto:MNWills@taylorcorp.com]
> Sent: Monday, February 18, 2002 1:51 PM
> To: 'rpg400-l@midrange.com'
> Subject: RE: Optional Parameters in Subproceedures
>
>
> Thanks, one more question. How can I tell if that parameter
> was passed or
> not?
>
> -----Original Message-----
> From: Bob Cozzi (RPGIV)
> You need to add the OPTIONS(*NOPASS) to the parameters that are
> optional.
> Remember, that when you decide a parameter is options, all subsequent
> parameters on the prototype/procedure interface must also be optional.

As an Amazon Associate we earn from qualifying purchases.

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.