My guess: Probably because the HLL compilers generated (and still do, unless told otherwise via PARM option) non-reentrant code that self-modifies. Ditto many compiler runtime modules.
Peter -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Paul Gilmartin Sent: Friday, March 01, 2013 11:16 AM To: [email protected] Subject: REFRPROT History Question I understand, diachronically, why REFRPROT was made an option: to maintain compatibility with existing "dusty deck" load modules. Where the source no longer existed. And the modules were linked NE. But why, in the beginning, as soon as the REFR attribute was available, were not all load modules, even from non-APF authorized libraries, loaded into write-protected storage? Just curious, gil -- This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
