The RENT attribute is not ignored for unauthorized programs. The program is still treated as reentrant (no new LOAD; no wait for completion of other processes), only the write protection is not set.
Now consider the following: We have modules that try to improve performance by doing complex computations only once. The modules are RENT, because they are used in a dialog environment. This is usually implemented by having a static pointer which is initialized with zero. The first time the module is called the static pointer is inspected. If still zero, the computation has to be done and in the end the static pointer is changed to the location of the result (usually a table of results, depending on the various inputs). We call this a "Gedaechtnis" (german for memory). The worst thing that could happen if the module is called in parallel is that the computation is done multiple times. If the module has completed the computation, it checks again the pointer, and if now not zero, it throws away its results, because another process has already completed the computation. For a logic of this kind, I need RENT programs which can be changed. Kind regards Bernd Am Sonntag, 22. Oktober 2006 19:16 schrieben Sie: > On Sun, 22 Oct 2006 09:19:36 -0700, Edward Jaffe wrote: > > I've never understood why the CsvRentSp252 DIAG trap is necessary. What > > is the rationale for ignoring the RENT attribute for unauthorized > > programs? Authorized or not, a RENT program that modifies itself in an > > unserialized way has a bug that could have serious ramifications for the > > application. IMHO, by ignoring the RENT option for unauthorized > > programs, the operating system does their owners a great disservice. > > I feel that way about various z/OS features. > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
