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.
--Dave
On 8/26/2014 3:52 PM, Micheal Butz wrote:
I have written one of those a while ago however I was hoping for something that
has an SDWA where
I can examine the problem
Sent from my iPhone
On Aug 26, 2014, at 4:48 PM, John McKown <[email protected]> wrote:
I guess you are talking about an ESTAEX type environment. If you have
the proper authority, you can make yourself a "resource manager" and
request that an exit be driven when the task or address space
terminates.
ref: http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/iea2a8b0/18.5.6
<quote>
MVS provides resource managers that are invoked to "clean up"
resources associated with a task or an address space. A resource
manager is a routine that gets control during normal and abnormal
termination of a task or an address space. Task or address space
termination is the process of removing a task or address space from
the system, releasing the resources from the task or address space,
and making the resources available for reuse.
</quote>
On Tue, Aug 26, 2014 at 3:23 PM, Micheal Butz <[email protected]> wrote:
Hi
I have a program which one of the first things I do is establish recovery
Durning the course of program
I invoke many system services
How can I be sure that my
Recovery routine will get control
Since it is quite possible my
Routine is not the last on the scb
Chain and if the last routine doesn't percolate I wouldn't get control
Sent from my iPhone
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
--
There is nothing more pleasant than traveling and meeting new people!
Genghis Khan
Maranatha! <><
John McKown
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] 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
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] 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
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
