Indeed, OS/360 had some code that was reentrant but not refreshable; AFAIK IBM has cleaned up all such abominations, and the binder does not allow you to create a load module or program object marked as reentrant but not refreshaable.
-- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ________________________________________ From: IBM Mainframe Assembler List <[email protected]> on behalf of Binyamin Dissen <[email protected]> Sent: Tuesday, November 17, 2020 2:35 AM To: [email protected] Subject: Re: security with storage allocation under z.OS On Mon, 16 Nov 2020 18:35:29 -0700 Paul Gilmartin <[email protected]> wrote: :>On 2020-11-16, at 17:47:10, Dan Greiner wrote: :>> ... :>> So, the facility only applies to virtual addresses on newer models. As I recall, the development of this facility was requested by z/Linux in order to help avoid classic stack-overflow exposures; but, it obviously has applicability to other environments. (It was also introduced in order to "keep up with the Joneses — er ... I mean the Intels.) :>> :>Conversely, there's REFRPROT to prevent storing into programs :>marked REFR. Dismayingly, I believe REFRPROT is global and :>intrduces incompatibility with "dusty deck" programs erroneously :>marked REFR. That is a good thing. However, RENT alone does not (conceptually) require a module to be refreshable. -- Binyamin Dissen <[email protected]> http://secure-web.cisco.com/19AoSGhGCR9I2eaAlvNQjDjrGeYVI8ZnwKDIRJFUw1x7i6ftx0Yb12NJmP5eT2Te_OX9fUfESQIxioFXHlvBsg8Owy9vbkR7RMoW26HYBeIGic1jYsKU8DRLF1OFfdQp_zEwAACiSd1uyXFy2uOG9rHoc243dXs2vrw5CdrmeBK5ulvS-2te48-y_edoYLr3akyrUOeZfuRgv8iccGgnCCD68J9NzHpL9coOltM4z494TX4ENW-p0LE2xuah-y6czQqH9_IksxhmxpkRUHcvsmdYXixdWX3emhB_En5iHoPNdxlmOUzkooWN42sNutD_hXn6w30x70WPkGYBbSPqXh2vyR0aLfO5pyVR2erbVJ0Os_MZNbfGaapiimpq_js5F_Pb2xpAAYm86DXgBjXlX3CyoM5UEyGVEVWmZbTtIxsftsvuESs_jUryrMu8P_RH5/http%3A%2F%2Fwww.dissensoftware.com Director, Dissen Software, Bar & Grill - Israel Should you use the mailblocks package and expect a response from me, you should preauthorize the dissensoftware.com domain. I very rarely bother responding to challenge/response systems, especially those from irresponsible companies.
