Q1A,Q1B) 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.) A1A: Quibble: it is your exit *routine*, not your exit to which the answer applies: when CSVDYNEX service's recovery gets control. A1B: yes. FWIW, an abendnum of x'7FFFFFFF' in practice (admittedly not in theory) will also result in not disabling your exit routine.
Q2A,Q2B) Is any notification made available? Specifically an ENF? A2: No Q3) 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. A3: CSVDYNEX REQUEST=RECOVER is for uses of CSVDYNEX REQUEST=CALL,FASTPATH=YES You can set any type of recovery that works for the environment(s) in which your exit routine gets control. Peter Relson z/OS Core Technology Design ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
