Interpreting this question as a "why" and the "we" meaning those in this
audience who do use them, my company's product TableBASE uses data
spaces, which are accessed though access registers, to hold customer
data in virtual memory, both for data that is specific to the job step
(including batch, IMS/TM regions, CICS regions, DB2 SPAS) and for data
that is to be shared among multiple concurrent processes in the lpar.
It avoids having to acquire storage within the address space (and
possibly run into address space constraints) or CSA (similar
constraints). An advantage is that it is very unlikely to be
accidentally overlaid by an error in a user program, since the value set
in the access register is internal to our product and most high level
languages do not make access register usage available to users. Also any
executable code in the data space accessed though access registers
cannot be executed without first moving the code into address space memory.
On 2017-12-03 11:44 PM, Sudershan Ravi wrote:
Hi,Why do we use access registers?
Gary Weinhold
Senior Application Architect
DATAKINETICS | Data Performance & Optimization
Phone +1.613.523.5500 x216
Email: [email protected]
Visit us online at www.DKL.com
E-mail Notification: The information contained in this email and any attachments is confidential and may be subject to copyright or other intellectual property protection. If you are not the intended recipient, you are not authorized to use or disclose this information, and we request that you notify us by reply mail or telephone and delete the original message from your mail system.
