On Thu, 29 Mar 2018 08:15:18 -0400 Thomas David Rivers <riv...@dignus.com> wrote:
:>The documentation for "Subpool handling" from the Assembler Services Guide :>indicates that (for subpools 0-127, which are task-related) "when the task :>terminates, the system automatically releases any of the subpool from :>0 through 127 that are unshared and are associated with the task." :>It then goes on to note that the SHSPV and SHSPL option on the :>ATTACH/ATTACHX :>macro can be used to indicate that a subpool is to be shared (other than :>subpool 0 :>which is, by default, shared.) :>My question is the attribute of "shared" - once a subpool is marked shared, :>can it ever be marked non-shared again? Once all sub-tasks end, does it :>revert back to non-shared, and thus when the main task ends, would the :>subpool :>be released by the OS? Well, a shared subpool is one owned by another task (somewhere up the parent tree). When the "owner" ends, there are no more sharers, as they are forced to terminate if still active., :>I can't seem to find any commentary on that question... :>That is - if a multi-task address space shares a subpool; is it the :>responsibilty :>of the main task to release the shared subpool, or will the OS do this when :>the main task ends? When a task ends, all storage "owned" by the task is freed. CSA is usually not owned by the task, so it will not be freed (only exception off of the top of my head is for LOAD to GLOBAL). -- Binyamin Dissen <bdis...@dissensoftware.com> 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN
