>Is that true for address spaces with non-reusable ASIDs? The exposure is only partly the ASID. It is also the ASCB. Assume that the ASCB is freemained at end of address space. And thus that storage could potentially be reused as an ASCB for a new address space. But that assumption is not directly true.
We do need to be careful in terminology. In the question, what is meant by a non-reusable ASID? Is that an ASID for an address space that was not started with REUSASID=YES? Or is it an ASID that is made non-reusable (either temporarily or permanently) because of cross-memory considerations? For an ASID that is permanently non-reusable, yes, it is safe to use normal XM Post because the ASCB will not get freemained. And for a non-memtermable address space, that would apply too. But for just about anything else, if sticking with the wait/post protocol, do use IEAMSXMP when it is available. It is available on all supported releases (although at z/OS 2.1 and 2.2 it is via APAR. For those releases, unless you "know" that it is OK, use IEAMSXMP only when field ECVTSXMP is non-0). Peter Relson z/OS Core Technology Design ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
