I think I understand Open code is a scope just like a macro is scope In order to have the same variable / value in multiple scopes a GBLx is used
> On Jun 27, 2023, at 1:29 PM, Seymour J Metz <sme...@gmu.edu> wrote: > > No; if the macro doesn't have GBLx &FOO then it isn't part of the scope of > the global &FOO, even if there is a GBLx &FOO in open code. > > ________________________________________ > From: IBM Mainframe Assembler List <ASSEMBLER-LIST@LISTSERV.UGA.EDU> on > behalf of Joseph Reichman <reichman...@gmail.com> > Sent: Tuesday, June 27, 2023 12:44 PM > To: ASSEMBLER-LIST@LISTSERV.UGA.EDU > Subject: Re: Conditional assembly variable scope > > Sorry but I don’t follow > If LCLx &FOO is declared in open code > And also let’s say assigned a value the scope is the entire assembly > > If GBLx &FOO is declared inside a macro > And also say set > > It’s scope is too the entire assembly ? > > >> On Jun 27, 2023, at 12:09 PM, Seymour J Metz <sme...@gmu.edu> wrote: >> >> The scope of the global &FOO is those units containing GBLx &FOO, where a >> unit is either a macro or the open code. >> >> ________________________________________ >> From: IBM Mainframe Assembler List <ASSEMBLER-LIST@LISTSERV.UGA.EDU> on >> behalf of Joseph Reichman <reichman...@gmail.com> >> Sent: Tuesday, June 27, 2023 11:30 AM >> To: ASSEMBLER-LIST@LISTSERV.UGA.EDU >> Subject: Conditional assembly variable scope >> >> Would any know the difference in scope >> Of a local used in open code and a global used >> In a macro the both seem to have a scope of the entire assembly
