DB2 on Windows V 9.5 FIXPACK1 enterprise edition

We have a report that has been running WAY too long (according to the programmer)

Used to run an hour and all of a sudden it is running about 2 1/2 hours.

what is the best way to troubleshoot this? I'm just learning UDB. Is there a trace function that I can run to capture the SQL as the report runs? What other options for troubleshooting this are there? Any help would be greatly appreciated.

first of developer should be able to provide the SQL to you. If that fails... you can always create an event monitor and capture the SQL that is running. Event monitor is described nicely in the manual.

There are many things that can cause SQL to run longer then usual.
Look at the database changes that have taken place.
Data quantity change
SQL change
Architecture change

Those are just a few to begin with.

event monitor!!!! I think that's the ticket. Thank you!