Restricting STRSQL

Tags:
AS/400
DB2
STRSQL
Hi, we are using DBVisualizer to access DB2 in our AS/400. However, I want to create some user profile where they can't update/delete/insert in the tables but read only. How can we restrict the users use DBVisualizer for SELECT statement only?
Thanks in advance. Vinod.
0

Answer Wiki

Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

Discuss This Question: 3  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.
  • TheRealRaven
    The title reference "STRSQL", but the question asks about "DBVisualizer". The two are generally unrelated except that they both provide a SQL interface. Which is your question about?

    In general, if you don't want users to run UPDATE/INSERT/DELETE/ALTER statements against database tables, then don't grant the authority to run those statements to those users.

    If users have the authority, it's unlikely you can enforce an additional layer above that to be sure the actions don't happen. There are too many "doors" into the database to close them all.
    34,465 pointsBadges:
    report
  • MyDataTransfer
    hi
    thank for your reply.
    ya .i agree the title and description confusing...
    we are using Db Visualizer to access  DB2 in as400. i want to restrict some users from making any changes in the database . i need to give them permission to run just SELECT statement through DBV. i think it is useless to control this in DBV . so i was just wondering how can i do this from as400 , by limiting his authority with  GRTOBJAUT command or any other solution . 
    just curious to know if anybody can help me in this .
    appreciate your kindness .

    thanks
    Vinod.
    20 pointsBadges:
    report
  • TheRealRaven
    If your applications do not adopt authority, then it might cause serious trouble to revoke existing authorities for users. That is, if a user runs a program that needs to update a table and the program doesn't have its own authority to do the update, the user must have the authority or the program will fail.

    If that is your situation, then you can't remove UPDATE/INSERT/DELETE/ALTER authorities from users until you first fix the application authority.
    34,465 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

Thanks! We'll email you when relevant content is added and updated.

Following

Share this item with your network: