On Mon, 21 Sep 2020 at 16:23, Pierre Fichaud <pr...@videotron.ca> wrote:
> Tonu=y, > Yup,I got that from a friend of mine. > How about the process id ? > It seems that ASSBOASB points to an OCO area. > The OMVS address space block contains the thread id. > But I can't find a mapping of it. > Regards, Pierre. > Thing is, there can be more than one process and more than one thread in an address space. So the OASB logically can't point to *the* thread id. And the OASB seems to still be OCO. The OAPB (OMVS Address-space Process Block?) is an odd one in that it was at one time OCO, but then got released. (In passing, it seems that the BPXY blocks/macros were always released, and the BPXZ ones were OCO. But there are now four BPXZs in SYS1.MACLIB.) The OAPB has only a small handful of PI fields, but the whole mapping is there in PL/X, and it does contain the field OapbProcessID. The OAPB is pointed to by the OTCB, and presumably directly or indirectly by the OASB. But here you're into unsupported territory, with all the choices that implies. I have various little Rexx programs that go through this stuff on live systems and in dumps, but I wouldn't put them into production for anything. Tony H. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
