> Why can't GETMAIN LOC=32 call IARV64 as above > under the covers so that the only change I need to > make to my application code is replace LOC=ANY > with LOC=32?
Because there is not a sufficient financial benefit to IBM to spend the money to implement anything like that. > Note that IARV64 has a granularity of 1 MiB when > I would prefer GETMAIN granularity for 32-bit > memory. The IARST64 and IARCP64 interfaces provide more granularity for managing 64-bit storage. > Also note that the CVT offset that IARV64 uses to > do a PC call is not documented, so this is a > proprietary interface. The IARV64 macro is the documented interface. > In addition I would like to produce a load module > that is trimodal which still runs on MVS 3.8j and > MVS/XA and OS/390. The SVC 120 exists on all > these systems (and LOC=32 will be hamless on > all of them), but not the IARV64 PC call. These > systems don't have the required hardware to do > PC calls either. IBM has no interest in providing downward compatibility with MVS 3.8j, MVS/XA, OS/390, or with any architecture prior to zArchitecture. Jim Mulder z/OS Diagnosis, Design, Development, Test IBM Corp. Poughkeepsie NY ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
