Listening on ENF codes is a very common thing to do and you will find that RMF and ISV monitors do this sort of thing a lot.
If you are coding the routine that gets invoked when the ENF code occurs, you need to be fully aware of the environment in which you get invoked - for example : you may get invoked in SRB mode. My general advice here is to not try and do anything too clever in the ENF exit routine but just store away the bits of data you are interested in and notify your server address space to process asynchronously - maybe by some sort of event/request block on a queue or updating some counter somewhere. Rob Scott Lead Developer Rocket Software 275 Grove Street * Newton, MA 02466-2272 * USA Tel: +1.617.614.2305 Email: [email protected] Web: www.rocketsoftware.com -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Miklos Szigetvari Sent: 12 September 2011 10:52 To: [email protected] Subject: ENF (event notification facility) question Hi Reading the ENF descriptions, seems to me, for the first , a useful facility would be to listen to a number of ENF events, and send some "alerts" if something wrong. I mean SRM event or config change or SMF ended etc etc . To this "general alert" contradict the ENF description in some points: - you can define only one event code in the ENFREQ request - from the description "avoid multiple listener user exits" ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
