As Binyamin says, posting the code would go a long way to help. We are simply guessing on what you are doing and you are giving very little information about the problem.
ISPF does play a part in this because you said that you are getting an ISP message documenting the abend. Since your program BALR's to the called module, then you are not telling us the full story otherwise your ESTAE would catch the abend. ISPF's ESTAE should be after your ESTAE. If it's a simple case of BALR, then one of the following must be the problem: 1. ESTAE failed to get set. Check R15/R0 for failure to set ESTAE. 2. Your called program may have ESTAE 0 without establishing an ESTAE. 3. Your subprogram is calling some ISPF functionality that is abending. APF, running SUP, XMEM and running authorized do not affect RTM recovery. I suggest taking the SLIP dump I mentioned before. You can look to see if your ESTAE is being properly set and how some other ESTAE is getting ahead of you. Jon Perryman On Thursday, August 28, 2014 5:46 AM, Binyamin Dissen <[email protected]> wrote: > > >Post your code - in entirety. > >On Thu, 28 Aug 2014 08:05:23 -0400 Micheal Butz <[email protected]> >wrote: > >:>ISPF is not part of the equation >:>Is plain vanilla TSO >:>The second program is loaded and balr'ed to >:>The library is APF authorized >:> >:>My question is the abend occurs in a different environment then from where >the estae(x) was established >:>E.g XMEM authorized etc does the recovery rtn get control > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
