I got it.
This was my idea for just testing programs during debugging.
The macro simply reset rmode to 24 instead of getmain etc etc
This way the binder links it rmode 24.
As you said "The RMODE instruction just marks each section in the object
output",
It could just remark that section in the
I generally allocate a work area that begins with a save area and do an MVCL
that includes every DCB, DCBE and MF=L macro, then do a cleanup of pointers
that I can't set with MF=E.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
עַם יִשְׂרָאֵל חַי
נֵ֣צַח יִשְׂרָאֵ֔ל לֹ֥א יְשַׁקֵּ֖ר
On Sat, 2 Dec 2023 at 13:13, João Reginato wrote:
> Sorry guys
> my poor english may be causing misunderstanding.
>
Perhaps, but it's a lot better than my Portuguese. I think we can
understand it pretty well. :-)
> You're right, TPUT doesn't use DCB and doesn't need RMODE 24 neither.
> I
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
On 12/2/2023 7:19 AM, Peter Relson wrote:
In the RMODE=SPLIT case you can end up with one part of the executable in one
RMODE and the other part in another RMODE and V-Con's between the two parts are
resolved at module fetch time.
Which is BTW ultra-cool functionality! (Too bad they don't
I just thought it was odd that the continued comments column is different for
an instruction vs a macro.
Perhaps the difference is that the data in column 16 of the continuation line
of the macro invocation is actually part of the macro invocation, not a comment.
Consider:
MACRO
It sounds like the OP might not fully understand RMODE.
RMODE is a directive to the binder and loader of where in storage to place a
module.
As was mentioned, the granularity is on a section basis, and the directive is
applied at module fetch time when store is acquired into which to place the
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
Ok but it could be changed. Why not?
-Mensagem original-
De: IBM Mainframe Assembler List Em nome de
Ed Jaffe
Enviada em: sexta-feira, 1 de dezembro de 2023 17:01
Para: ASSEMBLER-LIST@LISTSERV.UGA.EDU
Assunto: Re: Reseting RMODE
On 12/1/2023 11:27 AM, Jon Perryman wrote:
> On Fri, 1
So why there is an RMODE instruction in HLASM?
If I use a DCB inside my pgm it must be defined in RMODE 24, right?
So how can I tell it to the binder at compilation time?
-Mensagem original-
De: IBM Mainframe Assembler List Em nome de
Tony Harminc
Enviada em: sexta-feira, 1 de dezembro
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
A machine instruction can only be continued by coding the
operands to the end of the line and using a continuation
indicator, so once a space or comment on the same line has been
encountered, anything starting in column 16 on the next line
could only be a comment and there is no ambiguity.
Some
12 matches
Mail list logo
