>>Anyone have a summary of what kinds of code we can move above the bar in z/OS 2.3? and >You can move code that invokes no services or invokes only services that >support RMODE(64) execution.
And that has basically been true since z/OS 1.13 via LOAD with ADDR64 What is available in z/OS 2.3 mainly involves "normal" fetch mechanisms (e.g., LINK, LOAD, ATTACH, XCTL) being supported for placing the module above 2G. Some specific services that support RMODE(64) execution: WAIT, the suite of AMODE 64 pause/release services, storage obtain linkage=svc and linkage=system. Services that support RMODE(64) execution are intended to indicate that within the environment section of their documentation. We have been seeking customer/ISV guidance on prioritizing services that are most important to support RMODE(64) invocation (Note that RMODE(64) invocation in no way implies that data that is provided can be above 2G). Note that, in a fair number of cases, "support" is mostly a matter of test verification for SVC-entry and PC-entry services (and branch-entry services that run in AMODE 64). Recovery routines must all be below 2G, as must timer exits, and likely many other non-module things. You might find that that leads you towards increased usage of RMODE=SPLIT program objects. Peter Relson z/OS Core Technology Design
