× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



The authority in STRQM applies only in that utility - if you use STRQMQRY, you can run any SQL statement in the *QMQRY you specify.

That *QMQRY can be what you created in opt 1 of QMQRY.

So I think the STRQM opt 10 authorizations are just plain silly.

By the way - QMQRY is NOT the STRQM environment - it is an object type that you can run using STRQMQRY - STRQMQRY is the replacement for RUNQRY, perhaps.

STRQM, as Rob said, is more like the replacement for WRKQRY. But I think a better replacement for actually USING QMQRY's is WRKQMQRY.


On 6/18/2012 11:37 AM, Alan Campin wrote:
You or security officer need to do STRQM and then take option 10. F10
gives you additional details and for your user profile you need to add
UPDATE command to your authorizations. The default is SELECT only.

Personally I think the whole thing is ridiculous. I can go into STRSQL
and issue any command I want but when I go into STRQM I can't issue
the same statements. Crazy.

On Mon, Jun 18, 2012 at 10:32 AM, Tom Hightower <tomh@xxxxxxxxxxx> wrote:
My user profile has *ALLOBJ authority. When trying to run a QMQRY job on an
SQL with an 'update' statement in it I'm getting the following message:

QMR0050 - You do not have authority to use UPDATE.

I've not used QMQRY before, but client wants to so I'm trying to get him
going.

These are the settings for my profile in QMQRY:

Default library for QM objects . . . . LOCATION Name, *CURLIB

Default object creation authority . . *LIBCRTAUT *CHANGE, *ALL, *USE

*EXCLUDE, *LIBCRTAUT

Authorization list

Run query mode . . . . . . . . . . . . 1 1=Interactive

2=Batch

Display run options . . . . . . . . . Y Y=Yes, N=No

Confirmation messages in QM . . . . . Y Y=Yes, N=No

Naming convention . . . . . . . . . . *SYS *SYS, *SAA

RDB Connection method . . . . . . . . *RUW *RUW, *DUW

Default library for QM tables . . . . *NONE Name, *NONE, *CURLIB

Query data output . . . . . . . . . . 1 1=Display, 2=Printer

3=File

Printer to use for output . . . . . . *JOB Name, *JOB

F4 for list

File to use for output . . . . . . . . *NONE Name, *NONE

F4 for list

Library . . . . . . . . . . . . . . Name, *LIBL, *CURLIB

Job description for batch run . . . . *USRPRF Name, *USRPRF

F4 for list

Library . . . . . . . . . . . . . . Name, *LIBL, *CURLIB

Commitment control level . . . . . . . 1 1=None, 2=Change

3=Cursor stability

4=All

5=Repeatable Read

Default query creation mode . . . . . 2 1=SQL, 2=Prompted

Show query sort sequence options . . . N Y=Yes, N=No
Default column names displayed . . . . 1 1=Column Names
2=System column
names


Thanks for any help.

TomH

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




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.