The 1st two GIG or 3 are used by the system and not available to the user , I forgot why but can read it up.
Gunter Hochreiter From: "John P. Baker" <jbaker...@comporium.net> To: ASSEMBLER-LIST@LISTSERV.UGA.EDU Date: 12/09/2010 12:28 PM Subject: Re: z/OS IARV64 Sent by: IBM Mainframe Assembler List <ASSEMBLER-LIST@LISTSERV.UGA.EDU> Bill, It seems that it has gotten a lot more complicated. As best I can determine, the rules now appear to be -- 2G thru 32G-1 is available for private memory objects, but only if USE2GTO32G=YES is coded (not documented, not supported for non-IBM use). 32G thru 288G-1 is available for private memory objects, but only if LOCALSYSAREA=YES is coded (new for z/OS V1R12); question: is this storage unconditionally available for private memory objects on releases prior to z/OS V1R12? 288G thru 2T-1 is available for private memory objects. 2T thru 512T-1 is available for shared memory objects. 512T thru 16E-1 is available for private memory objects. John P. Baker -----Original Message----- From: IBM Mainframe Assembler List [mailto:ASSEMBLER-LIST@LISTSERV.UGA.EDU ] On Behalf Of Bill Fairchild Sent: Thursday, December 09, 2010 11:13 AM To: ASSEMBLER-LIST@LISTSERV.UGA.EDU Subject: Re: z/OS IARV64 I misunderstood the meaning of "bar". I thought it was at 4GB, and it is really the 2GB virtual line. User private includes an area from 2GB to 2T, as shown in the diagram you reference, but the virtual addresses from 2GB to 4GB-1 will cause a program interrupt in z/OS on any attempt to access them. This 2GB area can be thought of as "reserved". Bill Fairchild ----------------------------------------- The information contained in this communication (including any attachments hereto) is confidential and is intended solely for the personal and confidential use of the individual or entity to whom it is addressed. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this communication in error and that any review, dissemination, copying, or unauthorized use of this information, or the taking of any action in reliance on the contents of this information is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail, and delete the original message. Thank you