"IBM Mainframe Assembler List" <[email protected]> wrote on
08/18/2023 04:10:51 AM:
> This can be worked around by ensuring that the comparison starts
> with something which is clearly a character value, for example:
>
> AIF ('Flag' EQ SYSATTRP('&FLAG')).GEN_IT
> or
> AIF (''.SYSATTRP('&FLAG') EQ 'Flag').GEN_IT
>
Thanks for that.
> I wouldn't use the program type value for this special case.
> I feel it is more appropriate to use it as part of a systematic
> data typing scheme, for example for debugging tools.
So, given that the other macros need to validate that the bit mask
flag was defined correctly, what would you say is the best method for
accomplishing that? ... a custom data type code different from the
IBM-defined standard ones? ...or, what?
> And I feel that the constraint of needing the definition to
> precede the reference is an unnecessary complication.
That isn't a constraint. My DF macro allows either situation --
the flag byte immediately precedes the bit masks OR the flag byte is named
and can be anywhere before or *after* the bit masks and locatable at
compile time. Meaning, my DF macro accepts an optional parameter that
names the flag byte.
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
>
> Jonathan Scott, HLASM
> IBM, Hursley
*********************************************************************************************
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.
*********************************************************************************************
