RE: Checking for missing parameters in CL

I learned the MCH3601 from Jim Slone. And it's all through the QUSRTOOLS
and now the licensed programs TAATool sells. With that I'm assuming it's
not dangerous, since Jim designed it in the first place.

That said, he did retire some years ago, things may have changed.


--
Jim Oberholtzer
Agile Technology Architects


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Dan
Sent: Wednesday, January 31, 2018 11:54 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: Re: Checking for missing parameters in CL

On Wed, Jan 31, 2018 at 11:48 AM, <dlclark@xxxxxxxxxxxxxxxx> wrote:

/* receive optional parameters */
CHGVAR VAR(&RUNOPT) VALUE(&OPTRUN) /* run option? */
MONMSG MSGID(MCH3601) EXEC(DO) /* parm not passed */
RCVMSG MSGTYPE(*LAST) RMV(*YES) /* remove escape +
message from job log */

Pretty sure I've seen somewhere in this list that using this method is a BAD
idea, that BAD things could happen trying to access the memory location of a
parameter that was not actually passed to the program. I personally have
not witnessed problems using this method, so I am excited about David's
finding.

- Dan
--
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: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at https://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