Sorry guys my poor english may be causing misunderstanding. You're right, TPUT doesn't use DCB and doesn't need RMODE 24 neither. I don't know where I read it. But I'm talking about change RMODE during the compilation time, before the binder.
Imagine a pgm that uses many macros and it may need or not "RMODE 24", depending on some parms. 1) The first macro sets "RMODE ANY". 2) Then calls macro2, macro3 and so on. 3) Suddenly, macroN uses a DCB for example, that must be defined as RMODE 24. 4) So, at this time, I want to set "RMODE 24" but the HLASM compiler sends that error message. 5) And the binder will use RMODE ANY from the macro1, wrongly. So I need to prevent it resetting RMODE DURING THE COMPILATION TIME, before the binder run. I hope it helps TIA João -----Mensagem original----- De: IBM Mainframe Assembler List <ASSEMBLER-LIST@LISTSERV.UGA.EDU> Em nome de Steve Smith Enviada em: sábado, 2 de dezembro de 2023 12:00 Para: ASSEMBLER-LIST@LISTSERV.UGA.EDU Assunto: Re: RES: Reseting RMODE This conversation is making less and less sense. Since when does TPUT use a DCB? On the original question: RMODE sets a flag on the module that ultimately tells program fetch to load your program above or below the line (or bar, these days). Once loaded, what do you expect to happen on an RMODE change? You want program fetch to somehow delete the above the line copy and reload it below? Sorry, but that's ridiculous. If you think your code needs to be RMODE 24 for any reason, then it must be always. sas On Sat, Dec 2, 2023 at 5:48 AM João Reginato <jb.regin...@gmail.com> wrote: > I use TPUT sometimes as a trace tool only and it uses a DCB that must be > below the line. > As I just use it in debugging situations, and inside a macro, that was > easiest to me do this way. > But the discussion is not the TPUT but RMODE. That was just a sample. > There are some other situations that need to change it. > I'll read more about RMODE(SPLIT). > thanks > >
