RE: Missing parameter -- RPG400-L

Subject: RE: Missing parameter
From: "Dennis Lovelady" <iseries@xxxxxxxxxxxx>
Date: Wed, 16 Dec 2009 09:55:04 -0500
List-archive: <http://archive.midrange.com/rpg400-l>
List-help: <mailto:rpg400-l-request@midrange.com?subject=help>
List-id: RPG programming on the IBM i / System i <rpg400-l.midrange.com>
List-post: <mailto:rpg400-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=unsubscribe>

%PARMS will work only in main procedure.

I'm pretty sure that's not correct.

%PARMS will work with any procedure that has parameters specified as
OPTION(*NOPASS).

For the MAIN procedure, %PARMS is the same as *PARMS (which I have
never actually used, just saw it in the manual).

David is exactly correct. Except that he implies an optional parameter is
needed in order to use %PARMS. (I think that was unintentional.) No such
rule applies.

There are times when it can be handy to test %Parms in a subprocedure
without optional parameters. Usually that sort of thing is done with future
planning in mind.

Regards,
Dennis Lovelady
http://www.linkedin.com/in/dennislovelady
--
"Experience enables you to recognize a mistake when you make it again."
-- Franklin P. Jones

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: Missing parameter , David Gibbs

This mailing list archive is Copyright 1997-2025 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.