Re: Checking for missing parameters in CL

[Dan <dan27649@xxxxxxxxx>]

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