Re: Blocking QM Queries Was: WRKQRY - getting the SELECT records date range to show in the title

Rob,

I agree. There is always the case of companies like the bank where my wife
works. Although she is a project manager, they only have access to Query/400
and QM is out of bonds. I really believe is due to the ignorance of their
Sys Admin and DB2 personnel (I often hit a wall every time she asks me for
help: no SQL, no QM, etc. It is a wonder they don't run S/36 on their 595!)

Regards,

Luis Rodriguez
IBM Certified Systems Expert — eServer i5 iSeries
--


On Wed, Jul 21, 2010 at 3:04 PM, <rob@xxxxxxxxx> wrote:

I see no need to block QM Queries any more than I see blocking Query/400,
Excel or any other host of reporting tools.

I can see blocking PARTS of QM Query. QM Query is not limited to SELECT.
It can also do UPDATE, INSERT, etc. But this is easily handled by
STRQM
10. Work with Query Manager profiles
2=Change
Select allowed SQL statements
The default is to only give them SELECT (unless they are an older user
migrated from V2R1).

Wouldn't you like this simple process in Query/400?
2=Basic
Grants ... limited access to the queries and report forms options.
Users can display and print query and report form definitions, and run
queries and reports, but they cannot create or change them.

Or change their "Display run options" to block them from outputting over
top an existing file?


Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com

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