Canceling report doesn't cancel on the DB2 side

[kglore]

Hi, we are implementing version 8.3 right now and have ran into a problem. We need a way to identify the user running reports on the DB2 (AS400) side. When a user runs a report it goes to our DB2 with the DB2 user id and IP address of the report server. There is no way to tell one job from another. This is a problem when a user cancels a report that they are running because we can't stop it on the DB2 side because all jobs look the same. Has anyone else ran into this before? 

I've been working with the DB2 DBA and we are wondering if there is a way to pass along the userid with the report requests?

[blom0344]

http://www.ibmdatabasemag.com/db_area/archives/1999/q2/99sp_conte.shtml.old

"To prevent users from running resource-hogging queries, DB2 UDB for AS/400 has a query governor that uses the optimizer’s estimated run time to prevent the initiation of queries exceeding the specified threshold. You can set thresholds dynamically for individual users or applications."

Your best bet is to set a threshold on queries generated by the Cognos application. That will make life much easier for the DBA