I know you did, I remember! I have no idea how I missed it. Too much glue sniffing that day, I guess. Sheesh. Maybe I wasn't thinking and checked for TRAP() in the server JCL and not the client JCL. Who knows.
Anyway, you present a good idea. I will try the try/catch again real quick to see if it helps. With the CEEHDLR now, I even have it returning to the instruction following the PC call using the "move resume pointer" function. Apologies again! David Logan -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Craddock, Chris Sent: Sunday, January 13, 2008 2:25 PM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: C++ recovery from (an otherwise) system abend > And, somehow, I managed to fail to notice my runtime JCL still had > TRAP(OFF). I have no idea how I fail to notice. I did ask specifically about that! Now that you have it set to TRAP(ON), you ought to at least give the try/catch thing a go again. It seems to me more likely to "work" with less fooling around than a CEEHDLR. You can always go (back) to the condition handler if the language primitive doesn't do what you need. CC ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
