Ed,

That works for the CALL only if the parameters are not in a dynamic area in a 
DSECT somewhere.  For the GETMAIN, note that the "L" for the literal loaded 
into R15 requires a base register able to address the LTORG area.

Peter

-----Original Message-----
From: IBM Mainframe Assembler List [mailto:[email protected]] On 
Behalf Of Ed Jaffe
Sent: Friday, April 05, 2013 4:03 PM
To: [email protected]
Subject: Re: Relative Branches / IBM macros

On 4/5/2013 12:39 PM, Bernd Oppolzer wrote:
> But there are some annoying exceptions:
>
> - normal IBM CALL generates inline definitions and LA instructions
>
> - IBM GETMAIN RC,LV=(R1) generates inline definitions and LA etc.

I had no problem with either of these macros in a jump-only program.

       CALL  (15),(CIASD,CIASD)
+         DS 0H
01-CALL
+         CNOP 0,4
02-IHBOPLTX
+         BRAS  1,IHB0791A                        LIST ADDRESS
02-IHBOPLTX
+IHB0791  DS 0F
02-IHBOPLTX
+         DC    A(CIASD)              PROB.PROG.PARAMETER @L2C 02-IHBOPLTX
+         DC    A(CIASD) @L2C 02-IHBOPLTX
+IHB0791A EQU *
02-IHBOPLTX
+         BALR  14,15                             BRANCH TO ENTRY POINT
01-CALL

       GETMAIN RC,LV=(R1)
+         DS    0H @P5C 01-GETMAIN
+IHB0789C DS 0H
01-GETMAIN
+         LR    0,R1               LOAD LENGTH @ZA07133 01-GETMAIN
+         L 15,=AL1(B'00000000',(0),(0),B'00000000')
X01-GETMAIN
+                                                 LOAD GETMAIN PARMS
+         SR    1,1                     ZERO RESERVED REG 1
01-GETMAIN
+         SVC   120                     ISSUE GETMAIN SVC
01-GETMAIN

--
Edward E Jaffe
Phoenix Software International, Inc
831 Parkview Drive North
El Segundo, CA 90245
http://www.phoenixsoftware.com/

This message and any attachments are intended only for the use of the addressee 
and may contain information that is privileged and confidential. If the reader 
of the message is not the intended recipient or an authorized representative of 
the intended recipient, you are hereby notified that any dissemination of this 
communication is strictly prohibited. If you have received this communication 
in error, please notify us immediately by e-mail and delete the message and any 
attachments from your system.

Reply via email to