INADDR was added to STORAGE OBTAIN in SP4.3.0 to support FORKing in POSIX. POSIX did VSMLIST in the source space to find out how storage is allocated, and then STORAGE OBTAINs with INADDR in the target space to create the same storage allocations in the target. At the time of the original POSIX (OMVS) project, that was being done by separate development team with a separate FMID, using what they could of existing MVS services and doing the minimum of changes in MVS itself.
By the time 64-bit virtual storage came along, Unix System Services was integrated into the MVS BCP, and internal interface was created for Unix System Services to ask RSM to do the FORKing of memory objects. So we have had no need for an INADDR-like function for 64-bit storage. Jim Mulder z/OS Diagnosis, Design, Development, Test IBM Corp. Poughkeepsie NY > From: "Joseph Reichman" <reichman...@gmail.com> > To: IBM-MAIN@LISTSERV.UA.EDU > Date: 03/13/2019 03:00 PM > Subject: Re: IARST64 in addrr > Sent by: "IBM Mainframe Discussion List" <IBM-MAIN@LISTSERV.UA.EDU> > > Wonder why this functionality is not available above the bar > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
