Re: Common routines and optional parameters

*NOPASS works great for the LAST parameters in the list. The problem is
with the earlier parameters which also may be included or not depending
on the situation.

On 4/2/2019 3:26 PM, dlclark@xxxxxxxxxxxxxxxx wrote:

If I understand what you're asking, you can use const and

*nopass

together -- you just have to check whether the parameter was passed, or
not. I create a local variable and put the value of the optional
parameter in that local variable depending upon whether the constant was
passed, or not. (Note that RPG does not attempt to evaluate the
conditions in a complex statement after one of them evaluates to False.)


if %parms < %parmnum(pLibrary) // if data library not passed
or %addr(pLibrary) = *null // or was omitted
or pLibrary <= *blanks // or is blank
or pLibrary = '*LIBL'; // or is *LIBL
else; // skip it, else
iLibrary = %trim(pLibrary); // save data library name
endif;


Sincerely,

Dave Clark

--
This is the RPG programming on IBM i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com