I have certainly done that. What is the specific problem? One approach is to let the macro define the total size of the data. Then when you want the data to be "real storage" just code MYRECORD DS CL(size from macro) and use the DSECT to address it field by field.
Charles -----Original Message----- From: IBM Mainframe Assembler List <[email protected]> On Behalf Of Paul Gilmartin Sent: Thursday, June 19, 2025 12:12 PM To: [email protected] Subject: Re: Using the same macro to create the DSECT and a table entry On 6/19/25 11:20, Mark Hammack wrote: > I just read Ed Jaffe's presentation from Share where he mentioned that > they have some macros that not only generate a DSECT but using the > same macro, generate data in the program. I can find (and have a few) > examples of doing that when the data occurs once in a program but am > drawing a blank on a good way to do that for multiple occurrences of the > macro. > ... 1) define labels only on zero-storage instructions (L DS 0F) and bypass them with AIF in the CSECT case. Or: 2) Use the upper-bound operand to limit the addressability of code and a different USING naming the CSEECT to address the DSECT/ -- gil
