Limiting (but not stopping) interactive query by user -- MIDRANGE-L

× 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.

Subject: Limiting (but not stopping) interactive query by user
From: Adam.Driver@xxxxxxxxxxxxx
Date: Thu, 4 Dec 2003 15:47:48 +1100
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

Hi Everyone,

I might be clutching at straws here, but we have a customer that's
requested us to limit interactive query by user; ie, they don't want to
stop anyone from using interactive query, just limit their impact on the
system based on CPU utilisation. We don't really want to use QQRYTIMLMT
because we don't want to limit batch run queries at all.

Does anyone know if this is possible? All suggestions most welcome.

Thanks in advance

Adam Driver
Technical Consultant
Kaz Technology Services
Level 7
66 Wentworth Ave
Sydney NSW 2010
Australia
Phone: +61 2 9844 0386
Fax: +61 2 9844 0333

A division of Kaz Group Limited - visit our website at www.kaz.com.au

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

RE: Limiting (but not stopping) interactive query by user , Elvis Budimlic
Re: Limiting (but not stopping) interactive query by user , Simon Coulter

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.