I've seen a lot of hard coded offsets in IBM macros. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 עַם יִשְׂרָאֵל חַי נֵ֣צַח יִשְׂרָאֵ֔ל לֹ֥א יְשַׁקֵּ֖ר
________________________________________ From: IBM Mainframe Assembler List <[email protected]> on behalf of Paul Gilmartin <[email protected]> Sent: Thursday, June 19, 2025 10:57 PM To: [email protected] <[email protected]> Subject: Re: Using the same macro to create the DSECT and a table entry External Message: Use Caution On 6/19/25 14:44, Steve Smith wrote: > In general, for allocating actual space, all you need is the alignment and > total length. You can use some form of USING the DSECT to address as many > as you like, and you keep the macro simple. > ... Might this be useful where the List form generates in write-protected storage, copied into obtained for the Execute form. Does the Execute form generally identify fields by labels or by hard-coded offsets? The latter complicates documentation, debugging, and service. -- gil
