Re: Setting as CSECT or on using

2023-12-22 Thread Seymour J Metz
From: IBM Mainframe Assembler List on behalf of Paul Gilmartin <0014e0e4a59b-dmarc-requ...@listserv.uga.edu> Sent: Wednesday, December 20, 2023 3:30 PM To: ASSEMBLER-LIST@LISTSERV.UGA.EDU Subject: Re: Setting as CSECT or on using On 12/20/23 12:58:41, Seymour

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
List on behalf of Tony Harminc Sent: Wednesday, December 20, 2023 2:46 PM To: ASSEMBLER-LIST@LISTSERV.UGA.EDU Subject: Re: Setting as CSECT or on using 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

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
;>> THANKS :>> :>>>//MHELP ENTRY TO STORAGE MODE :>> :>>> SYSTEM PARAMETERS: :>> :>>> //SYSVAR NAMELNTH VALUE (5 :>> :>>> //SYSNDX 004 0005 :>> :>&g

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
AMELNTH VALUE (5 > :>>> //SYSNDX 004 0005 > :>>> //SYSECT 006 GRECOV > :>>> //SYSLOC 006 GRECOV > :>>> //SYSTIME 005 18.04 > :>>> //SYSDATE 008 12/19/23 > :>>> -Original M

Re: Setting as CSECT or on using

2023-12-20 Thread Seymour J Metz
List on behalf of Joe Reichman Sent: Tuesday, December 19, 2023 7:53 PM To: ASSEMBLER-LIST@LISTSERV.UGA.EDU Subject: Re: Setting as CSECT or on using The macro was invoked in the context of unnamed csect However the Macro established CSECT would having a macro Whitin a macros solve this I guess

Re: Setting as CSECT or on using

2023-12-20 Thread Binyamin Dissen
;>> //SYSLOC 006 GRECOV :>>> //SYSTIME 005 18.04 :>>> //SYSDATE 008 12/19/23 :>>> -Original Message- :>>> From: IBM Mainframe Assembler List On :>>> Behalf Of Binyamin Dissen :>>> Sent: Tuesday, Dece

Re: Setting as CSECT or on using

2023-12-19 Thread Paul Gilmartin
On 12/19/23 20:12:56, Joseph Reichman wrote: The definition of the macro was before a CSECT was established the macro module from file192 established a CSECT When I established a CSECT before the macro definition the picked it up . Does the following do what you expect? Otherwise, what?

Re: Setting as CSECT or on using

2023-12-19 Thread Paul Gilmartin
On 12/19/23 20:12:56, Joseph Reichman wrote: The definition of the macro was before a CSECT was established the macro module from file192 established a CSECT When I established a CSECT before the macro definition the picked it up . I don't see your code. "file192"? I believe it's quite

Re: Setting as CSECT or on using

2023-12-19 Thread Joseph Reichman
The definition of the macro was before a CSECT was established the macro module from file192 established a CSECT When I established a CSECT before the macro definition the picked it up > On Dec 19, 2023, at 10:07 PM, Paul Gilmartin > <0014e0e4a59b-dmarc-requ...@listserv.uga.edu> wrote: >

Re: Setting as CSECT or on using

2023-12-19 Thread Paul Gilmartin
On 12/19/23 17:53:53, Joe Reichman wrote: The macro was invoked in the context of unnamed csect However the Macro established CSECT would having a macro Whitin a macros solve this I guess the first macro would establish the CSECT allowing me to use in the second macro . This is confusing.

Re: Setting as CSECT or on using

2023-12-19 Thread Joseph Reichman
GRECOV >> //SYSTIME 005 18.04 >> //SYSDATE 008 12/19/23 >> -Original Message----- >> From: IBM Mainframe Assembler List On >> Behalf Of Binyamin Dissen >> Sent: Tuesday, December 19, 2023 6:27 PM >> To: ASSEMBLER-LIST@LIST

Re: Setting as CSECT or on using

2023-12-19 Thread Tony Thigpen
//SYSTIME 005 18.04 //SYSDATE 008 12/19/23 -Original Message- From: IBM Mainframe Assembler List On Behalf Of Binyamin Dissen Sent: Tuesday, December 19, 2023 6:27 PM To: ASSEMBLER-LIST@LISTSERV.UGA.EDU Subject: Re: Setting as CSECT or on using You know what you failed

Re: Setting as CSECT or on using

2023-12-19 Thread Joe Reichman
List On Behalf Of Tony Harminc Sent: Tuesday, December 19, 2023 6:28 PM To: ASSEMBLER-LIST@LISTSERV.UGA.EDU Subject: Re: Setting as CSECT or on using On Tue, 19 Dec 2023 at 18:12, Joseph Reichman wrote: > When I use the following > Using ,12,10 > > comes up blank even though I

Re: Setting as CSECT or on using

2023-12-19 Thread Seymour J Metz
יִשְׂרָאֵ֔ל לֹ֥א יְשַׁקֵּ֖ר From: IBM Mainframe Assembler List on behalf of Joe Reichman Sent: Tuesday, December 19, 2023 6:33 PM To: ASSEMBLER-LIST@LISTSERV.UGA.EDU Subject: Re: Setting as CSECT or on using 2420+ PRINT ON 50 B240

Re: Setting as CSECT or on using

2023-12-19 Thread Joe Reichman
as CSECT or on using You know what you failed to include in the post. 'nuff said. On Tue, 19 Dec 2023 18:12:37 -0500 Joseph Reichman wrote: :>Hi :> :>When I use the following :> Using ,12,10 :> :> comes up blank even though I know it had been set :>Thanks --

Re: Setting as CSECT or on using

2023-12-19 Thread Tony Harminc
On Tue, 19 Dec 2023 at 18:12, Joseph Reichman wrote: > When I use the following > Using ,12,10 > > comes up blank even though I know it had been set > Thanks > Available only in a macro. Which makes some sense - what would be its use in open code? But you say it's blank? If you're in macro

Re: Setting as CSECT or on using

2023-12-19 Thread Binyamin Dissen
You know what you failed to include in the post. 'nuff said. On Tue, 19 Dec 2023 18:12:37 -0500 Joseph Reichman wrote: :>Hi :> :>When I use the following :> Using ,12,10 :> :> comes up blank even though I know it had been set :>Thanks -- Binyamin Dissen http://www.dissensoftware.com

Setting as CSECT or on using

2023-12-19 Thread Joseph Reichman
Hi When I use the following Using ,12,10 comes up blank even though I know it had been set Thanks