Yes, you have to be carefull.
But CALL doesn´t do that
-Mensagem original-
De: IBM Mainframe Assembler List Em nome de
Paul Gilmartin
Enviada em: quinta-feira, 14 de julho de 2022 17:25
Para: ASSEMBLER-LIST@LISTSERV.UGA.EDU
Assunto: Re: RES: YA MGCRE RCF?
On 7/14/22 13:11:38, João
On 7/14/22 13:11:38, João Reginato wrote:
Yes, all the lines coded after the OPSYN will treat the "LA" instruction as a "LAY" until
you suspend it with a new "LA OPSYN ,"
Mustn't one be careful with this sort of OPSYN because
some library macros branch around generated code using
absolute
022 11:30
Para: ASSEMBLER-LIST@LISTSERV.UGA.EDU
Assunto: Re: YA MGCRE RCF?
I've never used OPSYN. Can this technique be used with the execute form of the
CALL macro, so that the linkage items can be further away from the base
registers?
-Original Message-
From: IBM Mainframe Asse
To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
Subject: RES: YA MGCRE RCF?
You can code e new line with " LA OPSYN LAY" just before the original CALL.
Try it.
Regards
João
-Mensagem original-
De: IBM Mainframe Assembler List Em nome de
Steve Smith
Enviada em: quarta-feira, 13 de julho de
You can code e new line with " LA OPSYN LAY" just before the original CALL.
Try it.
Regards
João
-Mensagem original-
De: IBM Mainframe Assembler List Em nome de
Steve Smith
Enviada em: quarta-feira, 13 de julho de 2022 14:50
Para: ASSEMBLER-LIST@LISTSERV.UGA.EDU
Assunto: Re
I created a macro to generate parmlists with optional specification for how
an operand is addressed. Briefly,
CALLV program,(parm1,parm2,(parm3,Y),parm4)
where parm3 would be addressed with LAY instead of LA. The macro actually
just appends the 2nd operand to LA (i.e. 'LA(,2)'), so it's
[< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]
Print Reply
Mime-Version:
1.0
Content-Type:
text/plain; charset="UTF-8"
Date:
Wed, 13 Jul 2022 08:53:38 -0400
Reply-To:
IBM Mainframe Assembler List
Subject:
On Wed, 13 Jul 2022 12:27:06 +, Peter Relson wrote:
>Definitely the lack of an equate for R12 should be corrected (such as by
>adding an equate and a BASR R12,0). I'll get that taken care of.
>
Thanks. But I may have misled myself by seeing CSECT; USING *; ...; END,
and assuming a user
Definitely the lack of an equate for R12 should be corrected (such as by adding
an equate and a BASR R12,0). I'll get that taken care of.
Almost all macros expect some amount of addressability to static data for
certain invocations. That will not be stated for individual macros. That is why
ASSEMBLER-LIST@LISTSERV.UGA.EDU
> Subject: Re: YA MGCRE RCF?
>
> Well, that got terribly garbled. Trying a different way.
>
> On Tue, 12 Jul 2022 10:30:13 -0600, Paul Gilmartin wrote:
> >Do I have cause for an RCF here?
> >
> >In z/OS 2.5 MVS Programming: Aut
.
Charles
-Original Message-
From: IBM Mainframe Assembler List [mailto:ASSEMBLER-LIST@LISTSERV.UGA.EDU] On
Behalf Of Paul Gilmartin
Sent: Tuesday, July 12, 2022 3:45 PM
To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
Subject: Re: YA MGCRE RCF?
Well, that got terribly garbled. Trying a different way
Well, that got terribly garbled. Trying a different way.
On Tue, 12 Jul 2022 10:30:13 -0600, Paul Gilmartin wrote:
>Do I have cause for an RCF here?
>
>In z/OS 2.5 MVS Programming: Authorized Assembler Services
Reference, Volume 3 (LLA-SDU)
>IBM SA23-1374-50
>
>I see: MGCRE - Execute form
>
Do I have cause for an RCF here?
In z/OS 2.5
MVS Programming: Authorized Assembler Services Reference, Volume 3 (LLA-SDU)
IBM SA23-1374-50
I see: MGCRE - Execute form
|DOMTST CSECT R2 EQU 2 USING *,R12 LA R2,CMD R2 POINTS TO THE COMMAND
AREA MGCRE
13 matches
Mail list logo
