On May 29, 2022, at 08:13:16, Seymour J Metz wrote:
>
> I've run into IBM macros where there is an optional first parameter and a
> null value causes an error message; In such cases I've had to put a comment
> statement before or after the macro call to comment it. Too bad that there
> isn't a &SYSMISSING with the effect of treating the operand as missing rather
> than empty, e.g., "label FOO &SYSMISSING" would get 0 as N'&SYSLIST.
>
Are you willing to identify a specific example and its origin?
("IBM" or "non-IBM" might suffice.)
What about a couple RCFs?:
To the macro caller:
... Note that the comma causes two operands to bee passed to
the macro, possibly causing a syntax error.
To the macro author:
The solitary comma in the operands field recommended earlier
will appear as two null operands. Your macro should be prepared
To deal with this.
--
gil
