<snip> I think RTM does a RP and RP is setup for a 16 byte PSW you think they could of found 8 bytes in SDWARC4 </snip>
RTM does not do a "resume program" (RP instruction). Even if this were available for the decades that RTM has supported retry, it would not have been of any help whatsoever. If someone makes a business case for needing to retry to a 64-bit address *AND* preserve the contents of all 16 registers, that could be considered for the future. But it is fully possibly to accomplish retrying to a 64-bit address, as I have pointed out, as long as you are willing to sacrifice register 15 (or, if providing your own stub, any other register except perhaps register 0). There is no available reserved space in SDWARC4, as you could tell by looking. Adding things to the SDWA has cost (including negative ramifications to the amount of storage available below 16M), and potentially significant ramifications to things like the dump header. As a result, updates are not made lightly. If you set SDWAG64R15, and identify CVTBSM0F as the retry point, you also need to specify RETRY15=YES on SETRP so that reg 15 is available with your value when the CVTBSM0F BSM is issued. Peter Relson z/OS Core Technology Design
