Re: AW: Query using (too) much CPU

[rob@xxxxxxxxx]

As always Birgitta speaks the gospel.  And your first order of action 
should be to run the performance analysis on the query and find out what 
you can do there.

But if you choose to ignore this sound advice and insist on just a general 
shotgun of dropping run priority then you can do a WRKCLS, find the 
appropriate class and drop it there.  It "may" be class QPWFSERVER.  You 
should be able to verify this by having your tool execute the generic 
stored procedure CALL on the i to do a DSPJOB OUTPUT(*PRINT).  Find the 
JOBD and the SUBSYSTEM.  Do a DSPJOBD and record the routing data.  Take 
that routing data, and subsystem and do a DSPSBSD and look at the routing 
entries.  Match that class there to what you find in WRKCLS.

Rob Berendt