There are two different protection methods here, of different vintages. The older mechanism is using SP252, and hence key 0, for modules linked RENT and loaded from a privileged source. Back in OS/360 that basically meant linklist, but APF widened that.
The newer mechanism, REFRPROpartT, simply adds another option; it does not eliminate the older mechanism. What you are seeing is exactly what I would expect. Unfortunately, way back when IBM chose to repurpose S0C4 to report a gaggle of program interrupts unrelated to IC4; in particular, you get the same ABEND for a key violation and for a page violation, albeit with a different reason code. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 עַם יִשְׂרָאֵל חַי נֵ֣צַח יִשְׂרָאֵ֔ל לֹ֥א יְשַׁקֵּ֖ר ________________________________________ From: IBM Mainframe Discussion List <[email protected]> on behalf of Erik Janssen <[email protected]> Sent: Friday, May 3, 2024 11:46 AM To: [email protected] Subject: putting refreshable module in subpool 252 Hello Peter, you said: <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. </snip> I just noticed that my system does not have REFRPROT active, but my module does get loaded in subpool 252 (key 0, not fetch protected) if I put it in SYS1.LINKLIB. Is there an explanation why this happens? Is that because I put it in an APF authorized library? And from what I understand, enabling REFRPROT will put all refreshable modules in key 0, not fetch protected storage, regardless where they reside? Kind regards, Erik Janssen. ---------------------------------------------------------------------- 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
