Re: Setting as CSECT or on using

2023-12-20 Thread Paul Gilmartin
On 12/20/23 12:58:41, Seymour J Metz wrote: Why not MACRO ... LOCTR MEND . Doesn't LOCTR imply ? I don't believe it creates a duplicate-named location counter in a different section. Is there an RFE for PUSH CSECT, PUSH DSECT or PUSH LOCTR? . I think Tony's

Re: Setting as CSECT or on using

2023-12-20 Thread Seymour J Metz
Why not MACRO ... 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

Re: Setting as CSECT or on using

2023-12-20 Thread Tony Harminc
On Wed, 20 Dec 2023 at 13:46, Paul Gilmartin < 0014e0e4a59b-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

Re: Setting as CSECT or on using

2023-12-20 Thread Paul Gilmartin
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 is to allow the coder of a data area DSECT to

Re: Setting as CSECT or on using

2023-12-20 Thread Joseph Reichman
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 Thanks > On Dec 20, 2023, at 11:18 AM, Jonathan Scott > wrote: > > It is clearly documented that is set to the current > section name on entry to the macro and

Re: Setting as CSECT or on using

2023-12-20 Thread Jonathan Scott
It is clearly documented that is set to the current section name on entry to the macro and is not updated if the macro changes section. https://www.ibm.com/docs/en/hla-and-tf/1.6?topic=symbols-sysect-system-variable-symbol Jonathan Scott, HLASM IBM Hursley, UK

Re: Setting as CSECT or on using

2023-12-20 Thread Binyamin Dissen
Trying to explain is great. But try what I suggested. That way we can see all the moving parts. On Wed, 20 Dec 2023 07:58:23 -0500 Joseph Reichman wrote: :>I modified cbt file 192 :> :>Member GRECOV :> :>The members have a MODULE :> :>Macro it established a base reg and CSECT work area etc

Re: Setting as CSECT or on using

2023-12-20 Thread Joseph Reichman
I’m at work right now will get back to you later Thank you > On Dec 20, 2023, at 10:03 AM, Phil Smith III wrote: > > Joe, > > > > Your posts are incoherent, and lack much supporting detail necessary for > anyone to help you. Folks are trying anyway, but you're wasting their time > and

Re: Setting as CSECT or on using

2023-12-20 Thread Phil Smith III
Joe, Your posts are incoherent, and lack much supporting detail necessary for anyone to help you. Folks are trying anyway, but you're wasting their time and yours. Please post a description and sample code so we can understand, as others have repeated asked. A whole sample program can be

Re: Setting as CSECT or on using

2023-12-20 Thread Joseph Reichman
I modified cbt file 192 Member GRECOV The members have a MODULE Macro it established a base reg and CSECT work area etc The was not sublist ( for more than one base reg ) I modified that as GRECOV went to two base regs The sublist code was after the module macro had established a CSECT

Re: Setting as CSECT or on using

2023-12-20 Thread Seymour J Metz
It doesn't matter where the macro definition is, only where the invocation is. Also, where and to what is set? -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 עַם יִשְׂרָאֵל חַי נֵ֣צַח יִשְׂרָאֵ֔ל לֹ֥א יְשַׁקֵּ֖ר From: IBM Mainframe Assembler

Re: Setting as CSECT or on using

2023-12-20 Thread Binyamin Dissen
You have been given good advice. Create a minimal program that shows the problem. Based on the expansion shown, all you need is register equates and the CSECT statement. Source should be: COPY macroname - to place it in the listing WHATEVER CSECT