On 21/06/2013 8:17 PM, nitz-...@gmx.net wrote:
I've seen something similar when two tasks under a parent TCB both
attempt to do a mvssigsetup(). The second one (attach) fails because an
mvssigsetup() has already been done.
To quote highlander, there can be only one! IIRC, this was two POSIX(ON)
C programs in ISPF split screens. However, I recall both errno and
errno2 were set correctly.
Funny you should say that: The (LE) tcb that throws the dump was just attached
and it terminates again. Presumably what's called recovery prevents the address
space from really terminating. The second dump (they're always a pair) shows me
both abends, both of them under different TCBs. The old one isn't available any
more in the second dump.
It is anybody's guess where errno is hidden.
Probably in the attached task that failed. errno is in thread local
storage. This is due to supporting standards before POSIX et all and
also supporting multi-threaded programs. errno is a global but
globals don't mix well with threads.
It should be in the dump and and maybe the CEEDUMP will help.
Barbara
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
