On 2016-04-19 10:55, John McKown wrote:
I remember the days of products fighting over use of the CVTUSER and TCBUSER fields. Name/Token is much better. And is GUPI as well. I would hate for a vendor (Scott works for one) to use these. What I have done in the past, is to dynamically create a subsystem; which creates an SSVT. I can then use that area for my own stuff. But finding the SSVT from a "random" address space would probably cost as much, if not more, than using a Name/Token.
If Scott works for a vendor, it would be much more efficient for him to request an assigned word in the customer anchor table than to dynamically create a subsystem. Subsystems that exist for the sole purpose of providing an anchor for a data area add unnecessary overhead for all other subsystems. Assuming you are in AMODE 31, you can pick up an address from the customer anchor table with 4 machine instructions.
-- Regards, Gord Tomlin Action Software International (a division of Mazda Computer Corporation) Tel: (905) 470-7113, Fax: (905) 470-6507
