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:[email protected]] On Behalf Of Bill Fairchild Sent: Thursday, December 09, 2010 11:13 AM To: [email protected] 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
