Hi Chris, Below, you say that ALET's for other address spaces is not supported. Does this mean if I have ALESERV ADD in a non-pc program that switches to AR mode and setting the AR to this ALET is not supported? Is it somehow now a requirement that we use the special ALET's for PASN, SASN and HASN?
To help clarify for Paul: 1. STORAGE OBTAIN is owned by the address space specified by the ALET (PASN if not specified). 2. As for the owning TCB and TCBADDR= not specified, it's the standard TCB convention if ASN of storage is HASN otherwise it's the ASCBXTCB. 3. As for storage visibility, it follows the same constraints that you are familiar with (e.g. CSA is common and KEY0 & KEY8 is visible but non-CSA is not). 4. Automatic storage release is dependent upon the subpool as documented in the diagnosis reference. There are some undocumented exceptions (e.g. ATTACH SHSPL=). 5. Integrity - as with any privileged, you must take great care. XMEM adds a great deal of complexity and hidden gotcha's (e.g. a macro changes AR1). If you plan on using XMEM, I recommend you create standards to be consistent where possible. Also do only what is required while in xmem/ar mode. Those who maintain your code will be thankful. Thanks, Jon Perryman. ________________________________ From: Chris Craddock <[email protected]> a cross memory server address space, there are circumstances where that program might want to obtain storage in "another" address space - typically that would be in your home (HASN) address space, or perhaps in the secondary (SASN) address space to provide a place to return results. *ANY* other combination is outside of the supported software architecture. Most particularly, there is a popular fantasy that you can just create an ALET for another address space and "have at it". That just isn't supported at all. > The paragraphs in this section of "Using Extended Addressability" dont > seem to identify which Adress Space actually owns the storage. > After The User Program has issued the STORAGE OBTAIN with the ALET, > it seems to me the example is missing a SAC instruction when it accesss the >storage.
