On Tue, 8 Jan 2019 at 15:58, [email protected] <[email protected]> wrote:
> Rob Scott wrote Same situation but SASN=NEW, then the MVCP will attempt to > copy data from address X in > the *server* address space to some address Y in the server ASID. So besides > influencing the Address Space Number (ASN), it is my > understanding that SASN=NEW also temporarily inhibits secondary addressing.. Well... sort of. It doesn't "inhibit" the mechanism of secondary addressing, but that secondary space upon entry is going to be the same as the primary upon entry. To that extent it's the same mode that normal application programs run in. > Do I understand this correctly ? I'm not sure. SASN=NEW effectively inhibits the access to the caller's primary that would otherwise (i.e. with SASN=OLD) be available using instructions that are architecturally defined to access the current secondary. But it has nothing to say about whether you can access that caller's primary using other means. And of course you can change the current secondary, assuming ASN authorization allows you to do so. Tony H. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
