Re: Optional parameters in CLLE -- MIDRANGE-L

The biggest danger with MONMSG is that parameters are passed differently between programs and procedures. Today the routine is written to only handle programs - but what if down the road somebody decides to use it as a bound procedure?

For those readers who don't appreciate the difference I wrote a pice for ITJ recently which you can find here:

https://www.itjungle.com/2017/02/20/guru-parameter-passing-fundamentals-programs-versus-procedures/

It uses RPG examples but the principals are the same.

Oh - and I'm not sure and don't have time to check - but not all languages pass the minimal parameter descriptors that I think the CEE routines depend upon. Others probably know and hopefully will comment.

Jon Paris

www.partner400.com
www.SystemiDeveloper.com

On Mar 16, 2017, at 9:49 AM, dlclark@xxxxxxxxxxxxxxxx wrote:

"MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx> wrote on 03/15/2017
07:33:45 PM:

I have a couple of processes where I'd like to have one or two optional

parms.

In the past, I've just tried using them in a CHGVAR and monitor for

MCH3601.

But... I'm wondering if %address() can be used instead. I think it
would be cleaner. In my testing, I've seen hex zeros for the %
address of a non-passed parm. That seems to indicate a *NULL will
be returned. Since it's consistent and not a garbage address, I
would think I could count on that logoc.

As hinted at but may not have been made completely clear, %ADDR()
will work in *OMIT situations but will not work in *NOPASS situations. I'm
very content with depending upon MONMSG but since CLLE doesn't have a
built-in function for %PARMS() then others probably prefer to call the LE
routines.

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.
*********************************************************************************************
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: http://amzn.to/2dEadiD