In
<cae1xxdg7srbgtgd-lkwx7pwpzu_7gycjtv1e4ai4xzzybo3...@mail.gmail.com>,
on 11/28/2012
at 10:44 AM, John Gilmore <[email protected]> said:
>The functioning of LOAD and DELETE provide a convenient example
>of what this implies If I LOAD a reentrant program that is not
>already present in storage, it is loaded and its usage/invocation
>count is increased from zero to one. If instead it is already
>present in storage, having been loaded by someone else, its usage
>count is increased by one. If I then DELETE that program, its usage count is
>reduced
>by one; and only if that count is thus reduced to zero, i..e., if no one else
>is
>currently using it, is the storage occupied by this program recovered for
>reuse.
Nonsense; that's not even true for an authorized application that
specifies GLOBAL=YES; ownership is at the task and address space
levels. What is true is that the owning task can delete a module
loaded with GLOBAL=YES while code in another address space is
executing it and that tasks in the same address space can step on each
other..
--
Shmuel (Seymour J.) Metz, SysProg and JOAT
Atid/2 <http://patriot.net/~shmuel>
We don't care. We don't have to care, we're Congress.
(S877: The Shut up and Eat Your spam act of 2003)
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
