On Wed, 7 Aug 2024 at 14:38, Colin Paice < 0000059d4daca697-dmarc-requ...@listserv.ua.edu> wrote:
> I have a C program which runs control blocks looking at CPU Usage > > char *pJBNI; > char *pJBNS; > pJBNI = (char*)*(long*)(plASCB+ASCBJBNI); // for jobs > pJBNS = (char*)*(long*)(plASCB+ASCBJBNS); // for started tasks > #define ASCBJBNI 172L > #define ASCBJBNS 176L > > One or the other will be zero > Yes, but those are jobnames, not jobIDs. The job ID is in JSABJBID (ASCBASSB -> ASSBJSAB). But I think the OP's question was about the *format *of the job ID, and whether there's anything other than parsing the beginning of it to see what kind of address space is running. JES2 (and presumably JES3, but I don't know it) have their own flags for STC and TSU, but I don't think those control blocks are shared between the two. And in theory anyone can write their own JES with its own internal conventions. One clue is that TSO parse (IKJPARS) has a definition for the syntax of a jobID, and so to the extent that anyone cares about TSO commands these days, any JES-suppllied jobID would have to be consistent with that. Tony H. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
