If he's using the binder then requesting REFR will also set RENT, which will get him SP252, and hence key 0.
REFRPROT is an unrelated mechanism. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 עַם יִשְׂרָאֵל חַי נֵ֣צַח יִשְׂרָאֵ֔ל לֹ֥א יְשַׁקֵּ֖ר ________________________________________ From: IBM Mainframe Discussion List <[email protected]> on behalf of Peter Relson <[email protected]> Sent: Friday, May 3, 2024 7:59 AM To: [email protected] Subject: Re: Testdriving svc in key 9 (was: finding callers key in svc) <snip> I managed to show now that the code in the svc is correct, it indicated that the caller was in key 9. </snip> Perhaps share, to help others not make the system mistake, what had led you to believe that the code was not doing what you wanted. <snip> I've solved the testdriver issue now by marking that routine as REFReshable and put it in SYS1.LINKLIB. </snip> This behavior, when marking the module as refreshable, applies only when the REFRPROT option of PROGxx is active. That applies system-wide. As long as that is OK, and you have control of setting REFRPROT, have at it. Peter Relson z/OS Core Technology Design ---------------------------------------------------------------------- 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
