> Date: Sun, 17 Aug 2014 20:48:33 -0400
> From: [email protected]
> Subject: Re: How to assign length of generated instructions to macro variable?
> To: [email protected]
>
> The value of LENGTH defrined by J R can be assigned to an arithmetic
> set symbol, give it the imaginative name/identifier &alength. Then,
> calling the arithmetic [set-symbol] value of the input-length
> parameter &ilength.
>
> |&el seta 8 --error-mnote severity level
> |&match setb (&alength eq &ilength)
> | aif (&match).lengths_match --if so, ok
> |&abort setb 1 --no, set explicit quit switch
> | mnote &el,' . . . . ' --error mnote
>
> There is no language problem here, and the notion of triggering an
> assembly error as a surrogate for writing an appropriate, fully
> descriptive mnote is almost as ugly as that of triggering an ABEND by
> using an irrelevant divide-by-zero operation.
>
> John Gilmore, Ashland, MA 01721 - USA
===
I agree with all that you say. I was following up on Binyamin's
suggestion which nobody seemed to understand.
The OP is "enhancing" his old macro which builds a storage area
containing, among other things, macro list forms. Further, his
macro has an operand which declares a maximum length for
the storage it defines. He then eyeballs the assembly to see
if the maximum length has been exceeded. His enhancement
would be to automate this check and issue an MNOTE.
Again, this is not how I build control blocks, data areas, etc.
However, in the spirit of giving him what he was looking for,
I was merely trying to expand on someone else's suggestion.
