RE: Optional Parameters in Subproceedures -- RPG400-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Subject: RE: Optional Parameters in Subproceedures
From: "Wills, Mike N. (TC)" <MNWills@xxxxxxxxxxxxxx>
Date: Mon, 18 Feb 2002 14:50:33 -0600
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>

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.

Follow-Ups:

RE: Optional Parameters in Subproceedures , Bob Cozzi (RPGIV)

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.