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



Thanks guys. We did think of doing this, but the brief from the client is
to not limit query at all (not even job priority) UNLESS it starts hogging
interactive CPU.

Thanks

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



date: Thu, 4 Dec 2003 17:25:55 -0800
from: "Glenn Birnbaum" <gbirnba@xxxxxxx>
subject: RE: Limiting (but not stopping) interactive query by user

Adam,

One more thing about the suggestion below, you would need to do a RTVJOBA
and test for interactive vs batch before doing the CHGQRYA or CHGJOB.

Glenn

-----Original Message-----
From: Glenn Birnbaum
Sent: Thursday, December 04, 2003 5:19 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: Limiting (but not stopping) interactive query by user

How about creating your own RUNQRY command in a lib above QSYS.  It simply
front-ends the real RUNQRY with any combination of CHGQRYA and CHGJOB. Use
CHGQRYA to limit the amount of time, then maybe even lower the job priority
via CHGJOB at the start of your CPP and then change it back at the end of
the CPP.  Doesn't seem too complicated.....

HTH,
Glenn Birnbaum


As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.