If you are in a cross-memory environment and need to access the ASXB, the following options are available:
If you want the ASXB of the primary address space, locate the ASCB of the primary address space (for example, EPAR to extract the ASID, and the LOCASCB to get its ASCB, then use ASCBASXB to access the ASXB) If you want the ASXB of the home address space, use AR-mode with ALET=2, and PSAAOLD as the address of the ASCB If you want the ASXB of the secondary address space, you can use ESAR to extract the ASID, LOCASCB to get the ASCB address, and ALET=1 in AR-mode If you want the ASXB of a "random" address space, there are some things that are possible, and some that are not, depending on authority, depending on whether the target space is non-swappable. If the space is non-swappable, for example, and you can find its STOKEN (note that there is no general programming interface for returning to you the STOKEN of a random address space; in theory, something running in that space would have had to put it somewhere where you can access it), you could use ALESERV ADD to add the address space to your access list and use AR-mode with the returned ALET. This same information applies, basically, to anything in the private storage of an address space. Peter Relson z/OS Core Technology Design ---------------------------------------------------------------------- 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
