Why not
MACRO ... &SYSECT &SYSSTYP &SYSLOC LOCTR MEND Is there an RFE for PUSH CSECT, PUSH DSECT or PUSH LOCTR? -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 עַם יִשְׂרָאֵל חַי נֵ֣צַח יִשְׂרָאֵ֔ל לֹ֥א יְשַׁקֵּ֖ר ________________________________________ From: IBM Mainframe Assembler List <ASSEMBLER-LIST@LISTSERV.UGA.EDU> on behalf of Tony Harminc <t...@harminc.com> Sent: Wednesday, December 20, 2023 2:46 PM To: ASSEMBLER-LIST@LISTSERV.UGA.EDU Subject: Re: Setting &sysect as CSECT or on using On Wed, 20 Dec 2023 at 13:46, Paul Gilmartin < 00000014e0e4a59b-dmarc-requ...@listserv.uga.edu> wrote: > On 12/20/23 09:21:39, Joseph Reichman wrote: > > I understand if I want to make it work I’ll have to break up the macro > into parts finish the fest after I have a CSECT statement > > . > It works as intended as it is. I believe the design objective of > &SYSECT is to allow the coder of a data area DSECT to restore the > caller's environment before exit. > MACRO ... &N SETC '&SYSECT' &T SETC '&SYSSTYP' BLAH DSECT ... &N &T MEND is common enough in our code. I can't say I've tried it, but presumably it would work with an unnamed xSECT. Tony H.