And of course the traditional solution to this problem is MF=E/MF=L variants of the macro.
Charles -----Original Message----- From: IBM Mainframe Assembler List [mailto:[email protected]] On Behalf Of Charles Mills Sent: Friday, January 13, 2017 9:18 AM To: [email protected] Subject: Re: How to separate instructions and data generated in macro? Depending on how complex the generated data is it might be possible to generate it as a literal. The location of literal data is always somewhat separate from machine instructions and easy to control with LTORG and LOCTR. Charles -----Original Message----- From: IBM Mainframe Assembler List [mailto:[email protected]] On Behalf Of Peter Hunkeler Sent: Friday, January 13, 2017 8:27 AM To: [email protected] Subject: How to separate instructions and data generated in macro? I have an old macro I wrote in the late 80ies that generates code to invoke WTO with variable text. Initially, the macro did not generate reentrant code. Then I changed that quite a while ago, but did not care to separate the instructions from the data it generates. The code merely jumped around the static data. Although that code is never used in perfomance critical environments, I now want to separate instructions and data, just for the fun of it,to avoid cache trashing.
