Peter, (I feel thrilled that I can correct someone with a signature line like yours ;-)
>> No one has mentioned, as an aside, that this is not the proper thing to do for macros such as STORAGE when you have no code addressability. I did. The last line in my original post said that: >> >> And before someone points out that STORAGE does not need a base. >> >> It does in VSE (because it is too hard to copy the code from MVS to VSE). >> .. SYSSTATE ARCHLVL=2 ... I wish....see above >> ... using of register 15 as a base reg across a macro is very very >> very dangerous, Well, Since VSE-lab is unable for various reasons to change the code to more state of the art techniques - I am pretty save doing as above (the alternative is to change the macro-source or move the code to base-reg covered areas) >> I hope this was not going to be run on a production system because allocating key 9 CSA is a system integrity exposure. << Maybe in z/OS. In VSE it is a cheap trick to avoid problems when addressing "common" storage. Since VSE does always set CR bit 39 key 9 is open to everyone- always!. Given the choice of storing something for others with the option to change it from others as well with the storage-protect scheme as used in VSE- this is superior to any other key. -- Martin Pi_cap_CPU - all you ever need around MWLC/SCRT/CMT in z/VSE more at http://www.picapcpu.de
