Rob Scott wrote:
One of the BIG disadvantages of CSA is that too many programs are spending too
much time in Key0 and it is all too easy for them to splat all over someone
else's product anchor block.
I would like to be able to allocate my anchor block in CSA64 and feel safe that
only programs with correctly registered interest can alter it (key0 or not).
I was contemplating the idea of adding a "guard" page (via PGSER
PROTECT) before and after my most important CSA64 allocations to protect
against the most common type of overlays. (No pun intended.) That would
make any CSA64 allocation 8K (plus rounding) larger than it has to be --
not something I'd be inclined to do with CSA31 given the existing
resource constraint, but in the 64-bit world it might make sense!
Personally I try leave my code in key0 about as long as I would leave my 4 year
old son with a carving knife.
Hear! Hear! I recently went through and replaced a bunch of key0 code
with MVCSK instructions. More trouble. But, far less exposure.
--
Edward E Jaffe
Phoenix Software International, Inc
5200 W Century Blvd, Suite 800
Los Angeles, CA 90045
310-338-0400 x318
[EMAIL PROTECTED]
http://www.phoenixsoftware.com/
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
