On Thu, 31 Oct 2024 at 08:27, Peter Relson <rel...@us.ibm.com> wrote:
> Shmuel wrote: > TROO comes closest to doing what I want, but it has that pesky alignment > requirement. > > OK, I'll bite. What alignment requirement? Are you referring to this: > > From POp: > When the ETF2-enhancement facility is not > installed, the translation table is treated as being > on a 4 K-byte boundary. > When the ETF2-enhancement facility is installed, > the translation table is treated as being on a doubleword > boundary. > > ETF2 has been part of the architecture levelset for z/OS since z/OS 2.1. > Certainly that's what Shmuel is referring to. Normally of course there's no problem aligning the TRxx table to the (relaxed as of ETF2) doubleword boundary. But my suggested use of TROO uses the string data as the translation table (and a different table as the data), and such a string can typically be on any byte boundary. So it's just another thing that has to be tested for and perhaps adjusted, and that isn't free in terms of time or readability. Tony H. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
