Re: Restricting RUNQRY interactive -- MIDRANGE-L

I agree with Paul, but I think that both approaches in tandem make sense.

Al

Al Barsa, Jr.
Barsa Consulting Group, LLC

400>390

914-251-1234
914-251-9406 fax

http://www.barsaconsulting.com
http://www.taatool.com






                    Paul Tuohy
                    <tuohyp@attglobal.n       To:     midrange-l@midrange.com
                    et>                       cc:
                    Sent by:                  Subject:     Re: Restricting 
RUNQRY interactive
                    midrange-l-admin@mi
                    drange.com


                    05/08/02 06:40 PM
                    Please respond to
                    midrange-l






Vern, far be it from me to disagree with Al but......

The problem with restricting the RUNQRY command from running interactively
is that you also
disable the F5-Run key, in Query itself. This is of enormous benefit to
users.

Better to use the CHGQRYA command to restirct the amount of interacive time
that can be taken
by a RUNQRY.

Just my 2 cents (euro)

Paul Tuohy

Al Barsa/Barsa Consulting wrote:

> Might I suggest changing the command itself to disallow *INTERACT, *IMOD
> and *IPGM from the ALLOW parameter.  Adding a validity checker can cause
> hassles with security.  I used to use that technique, and I have now gone
> away from it.
>
> Al
>
> Al Barsa, Jr.
> Barsa Consulting Group, LLC
>
> 400>390
>
> 914-251-1234
> 914-251-9406 fax
>
> http://www.barsaconsulting.com
> http://www.taatool.com
>
>                     vhamberg@attbi.com
>                     Sent by:                  To:
midrange-l@midrange.com
>                     midrange-l-admin@mi       cc:
>                     drange.com                Subject:     Restricting
RUNQRY interactive
>
>                     05/08/02 01:30 PM
>                     Please respond to
>                     midrange-l
>
> We have added a validity checker to RUNQRY. When RUNQRY
> is run from a command line, the VCP gets called. When
> you take option 9 from WRKQRY, it does NOT get called.
> Anyone know why?
>
> BTW, option 8 of WRKQRY (Run in batch) does call it.
>
> TIA
>
> Vern
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email: MIDRANGE-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> or email: MIDRANGE-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email: MIDRANGE-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> or email: MIDRANGE-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.


_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
or email: MIDRANGE-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.