|
Try to create a RUNQRY (or STRQRY or any other command you are interested to limit) command in a personal library. Such a new RUNQRY would change the priority of interactive jobs to, let's say, 40 or 50. Kindest regards Domenico Finucci Fiditalia , Milano, 02- 4301-2494 -----Messaggio originale----- Da: Brad Bird [mailto:BBird@PRIMEINC.COM] Inviato: luned́ 11 settembre 2000 16.47 A: MIDRANGE-L@midrange.com Oggetto: RE: Restricted Interactive RUNQRY > Are they getting this message when they use F5 from within a query, using the > option from within WRKQRY to run the query interactively, or taking a menu option > that explicitly does a QSYS/RUNQRY? They had a menu option that did a RUNQRY that I changed to QSYS/RUNQRY, then they started getting the error message. It didn't matter where I had the RUNQRY command, even QTEMP, it still got the authority from the RUNQRY highest in the LIBL. > As an aside, I would highly recommend that you take a long hard serious look at > the CHGQRYA command before removing the ability to run interactive queries. Doing > this is like giving someone a gift of a Ferrari and then telling them that you > have disabled the gear box so they can only drive in 1st and 2nd gear. I basically agree with you on the removing of the interactive query abilities, but I am not the one responsible for this decision, it comes from the director of IT. :) I believe you should reprimand the offender(s) and not penalize everyone. http://www.primeinc.com ********************************************************************** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please reply to the sender of the message. The views expressed in this correspondence may not reflect the views of Prime, Inc. This footnote also confirms that this email message has been scanned for the presence of computer viruses. *********************************************************************** +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +--- +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
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.