I already have 3 LOCTR's (code, static data, and yonder (i.e. long displacement) static data. Since tables and stuff referenced only via adcons belong in the yonder LOCTR, I'd need a second yonder LOCTR to separate the table entries from the character strings, since the table entries need to be contiguous. I'll use &SYSNDX for the names, cache 'em, and generate them with a 'FINAL' type call.
Robert Ngan DXC Luxoft -----Original Message----- From: IBM Mainframe Assembler List <[email protected]> On Behalf Of Paul Gilmartin Sent: Tuesday, November 23, 2021 15:33 To: [email protected] Subject: Re: ASMA030E? On Nov 23, 2021, at 14:14:44, Ngan, Robert (DXC Luxoft) wrote: > > That complicates my code, where I wanted to do this to generate table > entries. Now I need a separate named field for each generated table entry! > Would a MACRO using LOCTR and &SYSNDX simplify it? > -----Original Message----- > Why can't I code: >> >> >> DC A(=C'blah') >> >> This give an ASMA030E error, but wanting the address of a literal string >> seems legitimate to me as I don't otherwise need a named field with this >> value. >> > Jonatnan Scott answered the same question a couple weeks ago. DC and > literals are handled by a single subroutine which is not coded recursively. > He cited a compromise between code complexity and perceived usefulness. --gil
