🚀 go-pugleaf

Hi,

   Well, this might not be current information, but as I recall the TCB
pointed to the TIOT, which has the 8-byte job name (or TSO login id). A
combination of the ASID, TCBADDR, and JOBNAME ought to be unique - no?

   Also, your MVS-daemon program (system task, in IBM parlance, ought to
be able to determine which TCBs are subtasks of which, per the pointers
within them. Good luck!


In article <ag129.1798.0012E61B@ucs.cam.ac.uk>,
A. Grant <ag129@ucs.cam.ac.uk> wrote:
>Girish B Maraliga (girish@schism.tay1.dec.com) wrote:
>>  Is there any data (similar to 'pid' in UNIX) available from the system,
>>  which uniques identifies a task (some of our jobs are multi-tasking) ?
>>  One solution we have thought is a combination of ASID and a pointer to
>>  TCB.  This is not satisfactory as a task which starts after the previous
>>  one, can be assigned the same TCB ptr.
>
>Yes but you can detect when the TCB pointer stops being valid,
>by using a subsystem end-of-task exit.  You can delete anything
>'owned' by your client tasks (e.g. an entry in a table, or a
>control block) so that reusing the TCB address appears as a
>fresh client.  Is this enough?