is my understsnding correct that the LE Error handler is activated but has Problems because of the 64 Bit Situation in the Ceecib and then the non handled 0c4 occurs? If so, would it help if you used your own LE Error handler? or modify the Ceecib contents in a sensible way before percolating to LE?
------------------------------------------------------------------------ Gesendet mit der Telekom Mail App <http://www.t-online.de/service/redir/email_app_android_sendmail_footer.htm> --- Original-Nachricht --- Von: Charles Mills Betreff: Can AMODE 31 C/C++ get a signal on a S0C1/4 in AMODE 64 assembler? Datum: 27.08.2017, 20:02 Uhr An: [email protected] Starting a new thread. Here is the fundamental problem. (If you were following the other thread -- I am now testing without my own ESTAE, just vanilla LE.) An AMODE 31 C++ program provides a signal handler. It will get driven for your basic S0C1 or S0C4. But if the C++ program calls an assembler subroutine that gets a S0C4 while in AMODE 64 it seems to boggle LE and the signal routine is not driven. At least that is what I am seeing. Does anyone know of a way to get LE to drive an AMODE 31 C/C++ signal routine even if the exception occurred in AMODE 64? Charles ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] <http://listserv.ua.edu> 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
