I believe that you have a misunderstanding of what "shared subpools" are.

Any task in an address space has addressability to private storage of any
other task. Nothing special is required for this.

A "shared subpool" is one where those sharing the subpool can directly
allocate and free the storage and the storage lives until the last user of the
subpool (which would be the initial parent task doing the ATTACH SHSP) ends.
The storage is not freed when the subtasks end.

There is no real concept of "subpools" in 64bit as the area is not
suballocated by the system.



On Tue, 21 Jan 2020 10:19:17 -0500 Joseph Reichman <reichman...@gmail.com>
wrote:

:>Under to 2GB bar the attach has a parameter SHSPV parameter to share storage
:>or subpool with another task in the same address space
:>
:> 
:>
:>Above the 2GB I am assuming I would need to do a GETSHARED request ?

--
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

Reply via email to