Re: Preventing users from RUNQRY Interactively

At 14:29 18/05/99 -0700, you wrote:
>IBM's Query/400 manual has three suggestions for preventing a user from
>running RUNQRY interactively.  These are found on the web at
>http://publib.boulder.ibm.com/cgi-bin/bookmgr/BOOKS/Qb3agg00/d.0
>
>1. Change the command RUNQRY so it doesn't allow any interactive
>environments.
>2. Change authority to the command so that users cannot run it at all.
>3. Create a copy of RUNQRY that is restricted (as in item 1 above), put it
>in a library other than QSYS, then make that library come before QSYS for
>those users who should be restricted.
>

I faced this same problem just recently.

The solution I implemented was based on the fact that the users I wanted to
prevent from running interactive queries did not have command line access.

In the menu program that the users run I substitued a preprocessing program
for the WRKQRY. In the program I execute a CHGQRYA immediately before the
RUNQRY Command, and alter the Query time limit to 5 minutes. This
effectively allows users to run those genuine "short" queries but prevents
runaway "freight trains".

Before this the program also changes the job message reply action to
default, so when a user attempts to execute a query greater than the time
limit the program message offering them the choice of continuing to run the
query is automatically answered with a "C"

After they exit query, the program changes the query attributes back to the
defaults, and changes the job message reply to whatever it was before query
was started.

Hope this gives you some more food for thought.

Cheers


+---
| 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
+---