I believe that you're thinking of REFRPROT, which refers to refreshable modules rather than reentrant modules. Note that the binder does not support marking a module as refreshable but not reentrant, although the linkage editor does.
-- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 עַם יִשְׂרָאֵל חַי נֵ֣צַח יִשְׂרָאֵ֔ל לֹ֥א יְשַׁקֵּ֖ר ________________________________________ From: IBM Mainframe Discussion List <[email protected]> on behalf of Lennie Bradshaw <[email protected]> Sent: Friday, August 23, 2024 1:11 PM To: [email protected] Subject: Re: Non-reentrant program not allowed (where?); Advantages of reentrant programs? In addition to what others have said, these days reentrant programs are usually loaded into store-protected subpools, even if they are not APF authorised. This protects the program from being modified by anyone else operating in the same address space, either accidentally or deliberately. As this was not always the case, and for compatibility purposes, it can be disabled for non-authorised programs, I believe. Lennie -----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Richard Zierdt Sent: 23 August 2024 17:20 To: [email protected] Subject: Non-reentrant program not allowed (where?); Advantages of reentrant programs? Some assembly textbook authors advise always writing reentrant code "because you never know if your program will be" [placed in some library / system space]. The question is: where (e.g. what libraries) must programs be reentrant to be "allowed in" ? Besides specific libraries (if any), are there other advantages to reentrant code ? Thanks -- Richard Zierdt Confidentiality Warning/Avertissement de confidentialité: This message is intended only for the named recipients. This message may contain information that is privileged or confidential. If you are not the named recipient, its employee or its agent, please notify us immediately and permanently destroy this message and any copies you may have. Ce message est destiné uniquement aux destinataires dûment nommés. Il peut contenir de l'information privilégiée ou confidentielle. Si vous n'êtes pas le destinataire dûment nommé, son employé ou son mandataire, veuillez nous aviser sans tarder et supprimer ce message ainsi que toute copie qui peut en avoir été faite. ---------------------------------------------------------------------- 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 ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
