×
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.
Jim,
Way back in 1994, 13 years ago, (when I was at another employer), IBM
configured our AS/400-iSeries with the query analyzer and some APIs.
Every IBM query was analyzed by the IBM query analyzer to estimate how
long it would run.
One jobq was for quick queries, those that the query analyzer estimated
would run in less than 15 minutes.
The other jobq was for queries requiring more than 15 minutes.
Submitted jobs were estimated by the analyzer and killed if submitted to
the wrong jobq.
If the estimate was wrong and a job actually exceeded 15 minutes in the
quick jobq, the system would kill the job automatically and message the
user.
Users learned which jobq they were to submit to.
As an Amazon Associate we earn from qualifying purchases.
This thread ...
RE: Automatically killing long running jobs, (continued)
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
