>Tom, >In my code I have a need to be able to simultaneously access a number of >different control blocks, so I have a lot of registers tied up. No space >for more than one instruction base register, but I cannot limit the code in >a procedure to 4K. So I write baseless code.
>I tried breaking the procedures down. The code size grew dramatically. At >the same time, performance went to hell in a handbasket. MVCL and PLO >instructions tend to do that to you. >John P. Baker Ok, but it sounds more like a choice than an actual need. I have run into the same problem many times where you need access to many areas and those addresses kept for later use. To solve it, save address to save area, or if re-entrant, acquire some storage, save address in storage, then dsect storage...1 register. Sounds like many different ways to skin a cat to me. So I'm still trying to figure out how or why Baseless is "required" for the above need. How does Baseless eliminate the need or use of the MVCL instruction ?? Thanks, Tom Savor _____________ The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you. _____________
