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



Mike -

Segregate those users from the rest...

You can use a workstation name entry or transfer control at sign on so that those users run in a special subsystem, and then use a separate memory pool for that subsystem.

This new subsystem would need to have routing entries pointing to a class which throttles them down by using a run priority higher than the regular interactive users (perhaps 21 instead of 20) and a longer time slice (perhaps 2000, like a batch job) so that they don't thrash the system.

- sjl

"Mike Cunningham" wrote in message news:mailman.8808.1357845837.10847.midrange-l@xxxxxxxxxxxx...

Is there any means to set a CPU % utilization limit on a user? So their query can run no matter how long it might take in seconds but never be allowed to use more then X (say 10%) amount of the available CPU as reported on WRKACTJOB? I would not care if a query took 5 minutes to run as long as it did not keep other users from doing their work.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jim Oberholtzer
Sent: Thursday, January 10, 2013 6:43 AM
To: Midrange Systems Technical Discussion
Subject: Re: limit users doing queries with access. etc

Another option is the exit points for SQL/ODBC. In the exit program you can identify the user, and then set job level constraints by the user rather than globally like the query limit attribute does.

Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


On 1/10/2013 2:55 AM, McGovern, Sean wrote:
Check out CHGQRYA QRYTIMLMT.


-----Original Message-----
From:midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf
Oftim.dclinc@xxxxxxxxx
Sent: 10 January 2013 05:33
To: Midrange Systems Technical Discussion
Subject: limit users doing queries with access. etc

we have certain users who use access to query the iseries. A few times the user brought the system down to its knees.

is there a way to limit the resources a user can use when doing queries in this manner?
--
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.