I would suggest that your eastex has a bug. Did you examine the dump?
And, as usual - show the code. On Tue, 26 Aug 2014 18:02:01 -0400 Micheal Butz <[email protected]> wrote: :>It hasn't retried :> :>I establish an estaex in the begining :>Of My program then load another program :>The second program gets a S0C4 :>I get an ISP message re a S0C4 and the program ends my routine :>Never has a chance to examine :>It point is if everything is still under the same TCB/RB I should get control :> :>Sent from my iPhone :> :>> On Aug 26, 2014, at 5:53 PM, Binyamin Dissen <[email protected]> wrote: :>> :>> Why? :>> :>> If the called service successfully retries, it has handled the situation. Why :>> does your program, as the caller of the service, care whether there was an :>> abend? :>> :>> As usual the question is - "what is your business case?" :>> :>> On Tue, 26 Aug 2014 17:18:12 -0400 Micheal Butz <[email protected]> :>> wrote: :>> :>> :>I think the operative word here is :>> :>SHOULD :>> :> :>> :>I would like to establish the estatex once again close to the abend to get control :>> :> :>> :>Sent from my iPhone :>> :> :>> :>> On Aug 26, 2014, at 5:13 PM, Dave Day <[email protected]> wrote: :>> :>> :>> :>> Either I'm not understanding what it is you want to do, or you don't understand how this works. :>> :>> :>> :>> If you have an estae set on your currently executing program, it is the last on the chain, and the 1st to get control if your program abends. :>> :>> :>> :>> If you call another program from yours, and it establishes an estae, then that one is the last on the chain, and the 1st to get control if the called program abends. If it retries successfully, your estae will not get control. If it percolates, then yours gets called as it is the next in the chain. If retry is allowed, yours can retry, or percolate. :>> :>> :>> :>> As part of exit processing for any program that establishes a recovery routine, it should remove it, making the previous recovery routine the 1st one to get called in the event of an abend. :>> :>> :>> :>> --Dave :>> :>>> On 8/26/2014 4:01 PM, Micheal Butz wrote: :>> :>>> I have never tried estaex with the OV :>> :>>> Param but would that put my routine on top of the scb chain :>> :>>> :>> :>>> Sent from my iPhone :>> :>>> :>> :>>>> On Aug 26, 2014, at 4:57 PM, Dave Day <[email protected]> wrote: :>> :>>>> :>> :>>>> Set a SLIP to catch the abend in the system service. :>> :>>>> :>> :>>>> If the estae that gets control in front of yours successfully retries, then you have no knowledge in your program that the called service abended, unless it gives some kind of a return and reason code. :> :>---------------------------------------------------------------------- :>For IBM-MAIN subscribe / signoff / archive access instructions, :>send email to [email protected] with the message: INFO IBM-MAIN -- Binyamin Dissen <[email protected]> http://www.dissensoftware.com Director, Dissen Software, Bar & Grill - Israel Should you use the mailblocks package and expect a response from me, you should preauthorize the dissensoftware.com domain. I very rarely bother responding to challenge/response systems, especially those from irresponsible companies. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
