All %parmNum() does is convert the name to number at compile time. You could just do:
If %parms() >= 2;
Not saying that's a good thing to do though...
-----Original Message-----
From: dlclark@xxxxxxxxxxxxxxxx [mailto:dlclark@xxxxxxxxxxxxxxxx]
Sent: Tuesday, October 04, 2016 12:32 PM
To: RPG400-L <rpg400-l@xxxxxxxxxxxx>
Subject: Examine Parms in a Loop
In RPG, I'm familiar with %addr, %parms, and %parmnum for testing parameters to make sure they were passed to the program or procedure and have a valid address. For example:
if %parms < %parmnum(pMyData) // if parm not passed
or %addr(pMyData) = *null; // or was omitted
else; // skip it, else
// do something
endif;
But I have a large number of parameters that I would like to be able to examine in a loop -- rather than have to code each test individually and repeatedly. Is there a way I can check the address of a parameter by its parm number rather than by its parm name? Thanks.
Sincerely,
Dave Clark
--
int.ext: 91078
direct: (937) 531-6378
home: (937) 751-3300
Winsupply Group Services
3110 Kettering Boulevard
Dayton, Ohio 45439 USA
(937) 294-5331
*********************************************************************************************
This email message and any attachments is for use only by the named
addressee(s) and may contain confidential, privileged and/or proprietary information. If you have received this message in error, please immediately notify the sender and delete and destroy the message and all copies. All unauthorized direct or indirect use or disclosure of this message is strictly prohibited. No right to confidentiality or privilege is waived or lost by any error in transmission.
*********************************************************************************************
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.