The Exec DPE992C work with MVDB2 monitors, that is when a monitor discovers an exception condition it can issue a WTO, monitors relates to the individual target such as a single DB2 region hence the IMFJOB will be correct.
For Alarms, they are managed by Alarm Manager which resides in the Coordinating Address space (CAS) and as such the IMFJOB is the started task name.
You can still create an Alarm that generates a WTO with the Victim/Holder DB2 member names in the message text. These DB2 member names reside in LKEVENT as view elements. When you go into LKEVENT enter CUSTomize on the view and then "E" for show excluded elements:
You can see elements Victim MemberDB2 and Block MemberDB2, if you move your cursor to these fields and hit PF1 you will get the element names LKOGMEM and LKOUMEMH. You can then update your Alarm Manager definition WTO field to include &LKOGMEM VICTIM and &LKOUMEMH HOLDER as per the screen shot below
You would have to modified the DPE992C or create a new AO rule to pickup the Alarm Manager WTO and set Alerts or fire off some other task that you may want to do.
I hope this helps.
Thank you for your response. I have been working with 992c to squeeze my alarm into the template, but it didn't fit. So I copied it, and made modifications to parse out the information from the alarm message text. It is working just fine.
The other thing I learned is that we definitely need to have standards for messaging for ad-hoc alarms ao that they parse correclty.