×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
I have been asked to look into how to control adhoc queries from a
performance perspective.
System is V7R3
A good solution would be to automatically cancel a query if it exceeded a
length of execution time or configurable parameters.
I have been doing lots of reading and came across an article by Kent
Milligan
https://www.mcpressonline.com/analytics-cognitive/db2/techtip-routing-away-your-qzdasoinit-troubles
This explains how I could route QZDASOINIT prestart jobs to a different
sub-system based on user profile or group profile and set that subsystem
up with appropriate resources so as not to affect the entire system when a
user requests a query that brings the entire system to a standstill.
However just about every user has access to the query builder so maybe not
the best option.
The query builder is a third part tool that connects to a QZDASOINIT job
to execute the query and I believe then issues a sql statement against the
database and receives the result set. I am guessing JDBC connection.
While a brute force approach would be to check these jobs every five
minutes or so using a job information API I am hoping for a more proactive
approach where the system can notify of the situation and steps can then
be initiated to control or cancel the job.
Any suggestions would be appreciated.
Don Brown
midrange.com
