Each LPAR is from the OS's point of view another box on the other side of the computer room. (Yes, you can quibble with that but it is a good way of thinking about it for most practical purposes.) z/OS on LPAR A has almost no knowledge of or visibility into LPAR B. LPAR B, after all, might not be running z/OS: it might be running Linux, or VSE, or VM, or a standalone dump, or some new OS that I am writing in my spare time.
Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of R.S. Sent: Wednesday, November 27, 2019 12:20 PM To: [email protected] Subject: Re: Sysplex SP231 is a part of address space. It is virtual memory. LPAR is "hardware", so LPAR memory is real memory with no concepts like subpool, Common Area, PVT, etc. More: LPAR can host any operating system, including zLinux, which has no address spaces, SP231, LPA, etc. To repeat: NO z/OS MEMORY MAPPED TO PHYSICAL LPAR MEMORY CAN BE SHARED IN SYSPLEX. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
