If your dynamic exit has its own recovery routine and it recovers successfully, the the abend count will not be incremented and CSV430I will be avoided.
There is no documented ENF signal for any CSVDYNEX service. You have at least the following choices for notification of possible problems with your exit : (o) Periodically issue the LIST request to check on the exit status (o) Make your dynamic exit update a count field or STCK value somewhere every time it is invoked. (o) If you have a recovery routine for the exit, you could provide your own notification service to your server address space when it is invoked for an abend in the exit. I would probably choose the last option. Rob Scott Lead Developer Rocket Software 77 Fourth Avenue . Suite 100 . Waltham . MA 02451-1468 . USA Tel: +1.781.684.2305 Email: [email protected] Web: www.rocketsoftware.com -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Paul Schuster Sent: 25 May 2012 17:50 To: [email protected] Subject: CSVDYNEX ?'s The CSVDYNEX macro provides keywords ABENDNUM and ABENDCONSEC to control how many times the exit routine can abend before the exit is disabled. 1) At what point does the dynamic exit processing determine that an abend has occurred? If I were to provide an ESTAE or similar recovery routine in my exit, what that be sufficient to prevent the exit from becoming disabled? (Assuming it recovered correctly.) 2) Other than the CSV430I MODULE xxxxxxxx FOR EXIT IGGPRE00_EXIT HAS BEEN MADE INACTIVE DUE TO ABEND=xxxxxx REASON=xxxxxxxx message appearing, is any notification made available? Specifically an ENF? (I did not see any mention of that in the docs.) 3) If a recovery routine in the exit itself (as in (1) above) is not the answer, then what is the correct way to provide recovery? The CSVDYNEX RECOVER option seems to be only for callers of the exit; I am essentially only doing a CSVDYNEX ADD,STATE=ACTIVE. Thank you for any insight. Paul Schuster ---------------------------------------------------------------------- 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
