Umm... dont you maintain a table of your pthreads? Like storing off their ids somewhere?
If not maybe you should? Then you can have a routine in your exit that kills off the pthreads from the table using their id before you exit... Joe On Sun, Aug 9, 2020 at 6:14 AM Thomas David Rivers <[email protected]> wrote: > Thanks all! Turns out I was confused by the EC6 doc; > thinking the reason-code should be in R15. > > But - it's not - it's clearly where it needs to be... I'm > getting an EC6 ABEND with a REASON code of 0000FFFF > which means that the BPX _exit() was invoked with > subtasks.... (in this case, pthread subtasks.) > > Although - I _thought_ all the pthreads had been either > joined or detached. I didn't think a pthread TASK would > "stay around" (these are all HEAVY-weighted pthreads.) > > Is there some call that says "hey - end all the extent tasks > waiting on pthreads". (I don't have a pthread_t thread-id > because they have all "gone away" so I can't pthread_join > the thread or anything...) > > Or - do we just "live with" this EC6 ABEND in this case? > > - Dave Rivers - > > p.s To Peter - yeah - I should have said ESTAE... sorry for the inaccuracy. > > -- > [email protected] Work: (919) 676-0847 > Get your mainframe programming tools at http://www.dignus.com > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
