On Mon, 16 Jun 2014 11:17:23 -0500 Tom Marchant <[email protected]> wrote:
:>On Mon, 16 Jun 2014 09:53:13 +0300, Binyamin Dissen wrote: :>>On Sun, 15 Jun 2014 19:16:36 -0400 Peter Relson wrote: :>>:>A refreshable module, if treated as reentrant, will work (the :>>:>converse not being true, of course). A refreshable module, if treated as :>>:>serially reusable will work. :>>Not true. :>>Just because the module does not self modify, does not mean that it properly :>>serializes access to other storage. :>In that case, the module is broken, regardless of whether RENT and REUS are :>implied. In your scenario, if you have a module that is REFR,NORENT,NOREUS, :>and if those attributes are all honored by the system, CSV would bring in a :>new copy of the module for the second usage, and the damage would still be :>done. It need not bring in a second copy, as the first copy is unaltered. It would protect against a memory error in the program storage, where the system can simply bring in a new copy to another page and let it rip. :>The failure to serialize its usage of other storage means that it does not :>behave correctly. As it is neither marked reentrant or reusable, it has no requirement of serialization. -- Binyamin Dissen <[email protected]> http://www.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. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
