I think the "program type value" would be more appropriate for that purpose. Although I don't see much benefit as stated, maybe it could lead to some.
sas On Thu, Aug 17, 2023 at 12:19 PM Dave Clark <dlcl...@winsupplyinc.com> wrote: > Sorry, I shouldn't keep using that other thread since we are no > longer talking about the original subject. Anyway... > > Now that I'm using my own macro (DF) to generate the equated bit > mask, how does the assembler community feel about using expression-3 in > the EQUate instruction to define a custom data type that is not one of the > 28 IBM-defined data types? The manual states that this value can be 0 to > 255. > > Do I want to require that the DF macro be used if you're going to > use the SF, CF, and TF macros -- by testing for a unique data type > assigned by the DF macro? If so, any guidelines for selecting a unique > data type designation? > > Note that the programmer would still be able to use whatever > format (binary, hexadecimal, character, numeric, etc) for the bit mask > operand of the DF macro, but the DF macro would assign its own (override > the) data type for the resulting equated bit mask. > > > 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 > > > > > ********************************************************************************************* > 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. > > ********************************************************************************************* >
