Craddock, Chris wrote:
Ed said
The main reason for using ASCBINTS is that it is accessible from the
address space that schedules the SRB. The TTOKEN of the "cross memory
owning" TCB isn't. That TCB and its TTOKEN reside in the SRB schedulee's
private area, thus creating a "chicken and egg" problem.
True, but Jim's point was for the SRB routine to save it after the first
schedule and arrange to pass that value as a parameter and use it for
validation on dispatch during the second and subsequent schedules. At
least that is how I interpreted it.
I agree this would work for "second and subsequent" schedules. I needed
something that would work for all schedules -- including the first
and/or only.
--
Edward E Jaffe
Phoenix Software International, Inc
5200 W Century Blvd, Suite 800
Los Angeles, CA 90045
310-338-0400 x318
[EMAIL PROTECTED]
http://www.phoenixsoftware.com/
----------------------------------------------------------------------
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
