Add a DECIMAL=[YES|NO] keyword and generate AR10 EQU 10,,,,AR
when DECIMAL=YES is coded. This seems like a poster child for implementing QUAL <http://bitsavers.org/pdf/ibm/7090/C28-6311-4_MAP_Oct64.pdf#page=24> from IBMAP <http://bitsavers.org/pdf/ibm/7090/C28-6311-4_MAP_Oct64.pdf>. RFE? -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ________________________________________ From: IBM Mainframe Assembler List [[email protected]] on behalf of David Eisenberg [[email protected]] Sent: Monday, March 13, 2023 12:36 PM To: [email protected] Subject: Symbol collisions in macro definitions I'm hoping that someone can advise us. We have a small number of applications requiring IBM's IHAARA macro. The macro unconditionally generates this statement: ARA DSECT ALLOCATION RETRIEVAL AREA We also have a ubiquitous custom macro which generates register EQU statements. That macro is invoked from every one of our applications, and we can't easily get around that. Rather than equating access register 10 to symbol AR10, we do it this way: ARA EQU 10,,,,AR And that was fine for ages... until we tried using the IHAARA macro. It would be rather onerous for us to change the ARA symbol definition in our custom macro to prevent the name collision. Is there a recommended way to get around this in the small handful of our applications which must reference IHAARA? Any advice would be greatly appreciated; thank you! David
