Hello, on DB2 V9.7:

"The use of the CREATE EVENT MONITOR FOR DEADLOCKS statement and the
automatically started DB2DETAILDEADLOCK event monitor, to monitor
deadlock events, have been deprecated. Their use is no longer
recommended and might be removed in a future release."

Are there any DB2 people that can state why they are doing this? I am
curious if the DB2DETAILDEADLOCK event monitor causes performance
issues and that is why its being removed. Or..will the new format of
the Deadlock event monitor be performance intensive and DB2 doesnt
want to automate it?

Also, what "improvements" are there that they have to make "FOR
DEADLOCKS" (and all the other options) obsolete! Why make us all
change code to "FOR LOCKING" and why remove all the other options?
Are the rest just automatically included now. Has any used the new
event monitor and is it actually improved from the old?

Hi,

They have built a new and better one - so haveing the old potentially
running in parallel is useless and a overhead you can get rid of.

There is a whole bunch of new monitoring stuff in Db2 9.7 and the main
goal was to make it perform even better.
This is why the postponed the result formatting to the time where you
are goindg to analyze it so this effort can be
avoided when capturing data.
Have a look at the new monitoring options in the db cfg - you will see
that there is a change to even specify that events
that have not produced a locktime out can be monitored - if some
application had to wait longer than a certain configurable time....
So it should perfom better and is more flexible - I think these are
valid arguments

If you want to know more about it I recommend the IBM DB2 9.7 update
class....

Best regards
Michael