Re: ALET=2

>Even if it's page fixed? Yes. (in part because "which private space" is unpredictable, as might be the cross-memory environment). That has been documented "forever" although not in all the places where it could have been. Peter Relson z/OS Core Technology Design

Re: ALET=2

On Mon, 5 Dec 2011 10:46:38 -0500 "Shmuel Metz (Seymour J.)" wrote: :>In :>, :>on 12/05/2011 :> at 08:28 AM, Peter Relson said: :>>DIE routines are expected not to reference private storage, :>Even if it's page fixed? Well, I guess the DIE could build a DUCT that refers to private storage

Re: ALET=2

In , on 12/05/2011 at 08:28 AM, Peter Relson said: >DIE routines are expected not to reference private storage, Even if it's page fixed? -- Shmuel (Seymour J.) Metz, SysProg and JOAT ISO position; see We don't care. We don't have to

Re: ALET=2

To add a bit to what Jim Mulder posted, DIE routines are expected not to reference private storage, and therefore (whether they are I/O DIEs or Timer DIEs, whether they "can" or not) should not use ALET=2. Within z/OS, Home ASC mode would "work", although as with any DIE the

Re: ALET=2

In response to my question: >> Am i guaranteed that going into AR mode >> and setting a non-zero access register to 2 >> gives me access to the HOME address space >> through the corresponding GPR, no matter >> how many space-switching PCs are stacked >> up? >> >> If the answer to the question is "

Re: ALET=2

IBM Mainframe Discussion List wrote on 12/02/2011 05:48:18 PM: > Am i guaranteed that going into AR mode > and setting a non-zero access register to 2 > gives me access to the HOME address space > through the corresponding GPR, no matter > how many space-switching PCs are stacked > up? > > If t

ALET=2

Am i guaranteed that going into AR mode and setting a non-zero access register to 2 gives me access to the HOME address space through the corresponding GPR, no matter how many space-switching PCs are stacked up? If the answer to the question is "it depends", please try to be as clear as possible a