| Author |
Message
|
| RRR |
 Posted: Thu Apr 03, 2014 12:04 am Post subject: Read Access for application users in AS400 |
 |
|
Newbie
Joined: 25 Oct 2010
Posts: 8
|
Hello,
We want to restrict access for application users. They just want to connect to a Queue manager in AS400 and check the queue depth alone.
Using GRTMQMAUT command gave *CONNECT and *ADMDSP authorisation to the users. It works fine in the devl environment. But, it gives the below error when given in production.
Not authorized to command DSPMQM in library QMQM.
Error found on DSPMQM command.
 |
|
| Back to top |
|
 |
| bruce2359 |
| Posted: Thu Apr 03, 2014 5:34 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
Why do your application users need to display queue depth?
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| RRR |
| Posted: Thu Apr 03, 2014 6:25 am Post subject: |
|
|
Newbie
Joined: 25 Oct 2010
Posts: 8
|
| They just want to monitor the queue depth!!! |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Apr 03, 2014 6:28 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| RRR wrote: |
| They just want to monitor the queue depth!!! |
To repeat the question of my worthy associate, why are application people monitoring queue depth? As opposed to administrative or operational people?
If they see the depth as too low or too high, what do they plan to do about it?
IIRC (and my AS400 is well rusty) you can't restrict the permissions the way you're trying to. They get admin access to the admin commands (all of them) or they don't
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| RRR |
| Posted: Thu Apr 03, 2014 6:49 am Post subject: |
|
|
Newbie
Joined: 25 Oct 2010
Posts: 8
|
I think i should use the term "Application administrator" instead of "Application user".
Proactively they want to monitor the Queue depth in AS400 and take appropriate action in application.
And as i mentioned, we are successful in doing it in Devl environment. We are getting the error only in production environment. |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Apr 03, 2014 7:03 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| RRR wrote: |
| And as i mentioned, we are successful in doing it in Devl environment. We are getting the error only in production environment. |
Is the AS400 security configured the same way in both environments? It's possible your dev environment has security reduced or disabled.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| colbype |
| Posted: Mon Apr 21, 2014 11:21 am Post subject: I/5 Security |
|
|
Novice
Joined: 13 Jan 2009
Posts: 23
|
Most likely they have *ALLOBJ in Dev server which allows them to have authority to the commands in QMQM. All commands in QMQM are also in QSYS so just have them qualify the library and they should be fine.
If you check QMQM library authority they most likely have *PUBLIC (Exclude).
Better to have them use QSYS/WRKMQM anyways. |
|
| Back to top |
|
|
|
|
