Re: creating a new procedure that callanexistingprocedurewithoneadditional parm -- RPG400-L

Subject: Re: creating a new procedure that callanexistingprocedurewithoneadditional parm
From: "Paul Morgan" <pmorgan@xxxxxxxxxxxxxx>
Date: Wed, 27 Jul 2005 10:53:48 -0400
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/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>

Barbara,

Is this requirement to check %Parm more to do with ILE or with RPG?  Why
wouldn't the call using *NOPASS work like using *OMIT?

Use the example Charles gave in another message why should:

MyProc(parm1:*omit);
MyProc(parm1)

be any different?

Paul

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: creating a new procedure thatcallanexistingprocedurewithoneadditional parm , Barbara Morris

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.