> > REFRPROT in PROGxx causes REFR load modules and program objects > > to be loaded into key 0 storage, and the full 4K pages are page > > protected. RSECT is not involved. I would expect that the > > individual unprivileged programmer has control over whether he > > specifies REFR when he binds his program. > > > But he can not assure that they get loaded into protected > storage. That's up to the administrator.
The administrator should be specifying REFRPROT in PROGxx. The only reason we made it an option was concern that an installation might have self-modifying programs which were incorrectly had the REFR attribute, and we didn't want that to be a migration issue for z/OS 1.9, where REFRPROT was introduced. Jim Mulder z/OS System Test IBM Corp. Poughkeepsie, NY
