Re: Restricted Interactive RUNQRY -- MIDRANGE-L

Hi Brad, definately a strange one. I duplicated what you did and got the exact
same error.

1. Did a CRTDUPOBJ of the RUNQRY command to a library that is prior to QSYS in
the library list.

2. Did a CHGCMD to new RUNQRY command to disallow *INTERMED.

3. When I do a RUNQRY (new one) I get a
        CPD0031 Command RUNQRY not allowed in this setting.
        (Message sent from program QCARULE)

4. When I do a QSYS/RUNQRY I get a
        QRY2294 Specified option or F5=Report not allowed.
        (Message is sent from program QQUDA)

Of course, if I rename the copied command to TESTRUNQRY, everything works as
expected.

This would seem to indicate the query is doing some extra checking of its own -
and using the library list.

I am afraid I have no idea how to cure this or what exactly is happening in the
bowls of the RUNQRY process but I would suggest the following:-

Since you want this to apply to runqry commands being run directly from menu
options - have the menu options do a sbmjob of the runqry command instead.

Fall back on what I was saying about CHGQRYA for people using WRKQRY. Change 
your
menu option for user doing a WRKQRY to run the following CL program.

-------------------------------------------------------------------------------------------

Dcl        &InqMsgRpy   *Char  10

RtvJobA    InqMsgRpy(&InQMsgRpy)

ChgJob     InqMsgRpy(*DFT)
ChgQryA    QryTimLmt(180)

wrkqry

ChgJob     InqMsgRpy(&InQMsgRpy)
ChgQryA    QryTimLmt(*SysVal)
--------------------------------------------------------------------------------------

This give them a maximum of 3 minutes for an interactive query. If you want to
emulate the "no interactive queries" then set the time limit to 0 instead of 
180.

If you are tempted to change the system value (QQRYTIMLMT I think) be very
careful. It also applies to OPNQRYF and SQL.

Not a cure but I hope it helps

Paul Tuohy


Brad Bird wrote:

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


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