Craddock, Chris wrote:
Jim said
You could obtain and save the TTOKEN of the TCB pointed to by
ASCBXTCB.
At some point in the future, if the TTOKEN of the TCB pointed to by
ASCBXTCB matches the TTOKEN you save previously, then it is still the
same job step (because the TCB pointed to by ASCBXTCB terminates when
a job step terminates).
That's a good idea. A little known and certainly undocumented "oh by the
way" is that the left half (i.e. the first 8 bytes) of the TTOKEN is the
STOKEN of the address space where it lives. Ed Jaffe's idea of using
ASCBINTS is probably a good one too and it eats 8 bytes less :-)
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.
--
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
