For each section of code, you should have USING statements that reflect what registers are loaded in that code. They don't load the registers, but only inform the assembler of what to assume in that code.
-- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 עַם יִשְׂרָאֵל חַי ________________________________________ From: IBM Mainframe Assembler List <[email protected]> on behalf of Dave Clark <[email protected]> Sent: Wednesday, November 8, 2023 5:03 PM To: [email protected] Subject: Re: Internal Exit Routine Handling "IBM Mainframe Assembler List" <[email protected]> wrote on 11/08/2023 04:49:37 PM: > I don't understand. The USING is associated with the location in the > source where you code it, not with the location in the source where > you define the data. Perhaps my understanding of it is flawed or limited, and I also somehow have a different concept of how a USING applies to data vs. how it applies to code. But my logic seems to tell me that the USING has to be "active" at the time the branch instruction is executed. It seems the branch would not assemble if I DROPed the USING that covered the code (where the branch target was defined) before the point where I attempted to actually branch to it. Meaning, using your example, it seems the following would fail to assemble. Is this my misconception? If so, how does this relate to having to use an address constant with LOAD instead of just using LOAD ADDRESS -- as was mentioned? USING *,R11 TARGET DS 0H DROP R11 ... USING *,R12 B TARGET DROP R12 Sincerely, Dave Clark -- int.ext: 91078 direct: (937) 531-6378 home: (937) 751-3300 Winsupply Group Services 3110 Kettering Boulevard Dayton, Ohio 45439 USA (937) 294-5331 ********************************************************************************************* This email message and any attachments is for use only by the named addressee(s) and may contain confidential, privileged and/or proprietary information. If you have received this message in error, please immediately notify the sender and delete and destroy the message and all copies. All unauthorized direct or indirect use or disclosure of this message is strictly prohibited. No right to confidentiality or privilege is waived or lost by any error in transmission. *********************************************************************************************
