🚀 go-pugleaf

In article <3l4iht$fqk@nova.voicenet.com>, <hanisco@omni.voicenet.com> writes:
> 
> I don't have any mannuals in front of me at the moment, but I'm pretty
> sure you can get the JES2 job number without CMS.  Of course, this won't
> work in a JES3 environment.
> 
> If I remember correctly, you can pick up the JES2 job number from the JCT.
> Now, there are 2 JCTs, an MVS one and a JES2 one, so be sure to pick up the
> JES2 one.  I don't remember the addressing flow, but it's no more than 3
> pointers off of the TCB.
> 
> Mark
> 

Sadly the JCT is in the JOBS private address space. 

However one can get the jobnumber of an executing job by using the 
STATUS/OUTPUT SSI call. This will give you the equivalent output as from a TSO 
STATUS command. I can probably hunt up the code if you need it - I wrote it for 
a presentation some 5-6 years ago.

However this is not unique for a task. All tasks in the memory will use the 
same JOBID.

The TTOKEN is unique.