SNIP
That won't help.
To make it more clear, I have a local ASVT with a slot for each address space.
If a task needs my services I would like to track the address space (in the
ASVT slot) as well as a linked list of the tasks using the service chained off
of the ASCB slot. Additional tasks in this address space may be connecting and
disconnecting.
So if there is already an address space tracking block just chain the TCB
block off of it. If not, allocate one and anchor it. Of course, another task
may have the same idea and there might be two attempts at storing into the
slot. Or the cleanup procedure can detect that all tasks have disconnected and
thus there is no need to retain the address space tracking block.
SNIP
I have a similar function within my code, and use a LATCH to serialize.
When the server comes up, it defines the set of Latches needed. Both PASN=HASN
and PASN ne HASN code that runs in my address space use the latches. Seems to
work fine, as far as I can tell.
--Dave Day
----------------------------------------------------------------------
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
