The current implementation of IARV64 GETSTOR with USE2GTO32G=YES is to do a first-fit search from low address to high address of the 2GBTO32GB area. So if there is available space below 4GiB, that is what you will get. Since that implementation detail is not documented, it is not guaranteed to behave that way in the future. But I know of no plans or reasons to change that. Jim Mulder z/OS Diagnosis, Design, Development, Test IBM Corp. Poughkeepsie NY
> The IARV64 instruction probably will find > memory. But it will be a 64-bit address > requiring me to manipulate and save > 64-bit registers. I wish to write 32-bit > programs, and I also want those 32-bit > programs to run on OS/390 as AM31 > and on MVS 3.8j as AM24. Only on z/OS > and MVS/380 would my 32-bit applications > run as AM64 and obtain and use LOC=32 > memory. > On Mon, 7 May 2018 11:51:55 -0500, Steve Partlow <[email protected]> wrote: > > >To the original requirement of "support a LOC=32 parameter to > GETMAIN, giving 32-bit programs access to a full 4 GiB instead of > the current 2 GiB provided by LOC=31." > > > >Why not write your own routine to issue an IARV64 GETSTOR with > USE2GTO32G=YES and then GETMAIN if that fails to find storage? The > free could easily check the address being freed to decide which > service to use on release. > > > >---------------------------------------------------------------------- > >For IBM-MAIN subscribe / signoff / archive access instructions, > >send email to [email protected] with the message: INFO IBM-MAIN > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
