| Author |
Message
|
| MQAltaf |
 Posted: Thu Jun 02, 2005 5:46 am Post subject: AMQ8135: Not authorized error on AIX5.2 |
 |
|
Centurion
Joined: 10 Feb 2005
Posts: 119
|
Hi,
I receive the following error when trying to define a queue local logged is as root: -
AMQ8135: Not authorized
root is part of the mqm group and has the correct permissions set as shown below
dspmqaut -m QWDCPR7A -t qmgr -p root
Entity root has the following authorizations for object QWDCPR7A:
inq
set
connect
altusr
crt
dlt
chg
dsp
setid
setall
dspmqaut -m QWDCPR7A -t qmgr -p mqm
Entity mqm has the following authorizations for object QWDCPR7A:
inq
set
connect
altusr
crt
dlt
chg
dsp
setid
setall
Can someone possibly shed any light please
I have also recycled the queue manager but to no avail |
|
| Back to top |
|
 |
| sebastianhirt |
| Posted: Thu Jun 02, 2005 5:59 am Post subject: |
|
|
Yatiri
Joined: 07 Jun 2004
Posts: 620
Location: Germany
|
Hi,
make sure that you have also the necessary permissions 'inside' the queue manager.
You might want to check whether you have appropriate rights on the SYSTEM.DEFAUL.LOCAL.QUEUE
cheers Sebastian |
|
| Back to top |
|
|
| MQAltaf |
| Posted: Thu Jun 02, 2005 6:03 am Post subject: |
|
|
Centurion
Joined: 10 Feb 2005
Posts: 119
|
| The problem was resolved by recycling the queue manager which I though wasnt required. It doesnt state anything about recycling the queue manager in any documentation |
|
| Back to top |
|
|
| sebastianhirt |
| Posted: Thu Jun 02, 2005 6:07 am Post subject: |
|
|
Yatiri
Joined: 07 Jun 2004
Posts: 620
Location: Germany
|
Receycling in the meaning of recreating it? If that helped, you should have been reading the documentation that clearly states, if you change OS level permission type in refresh security 
BTW, Personally speaking I would try not to use root for any MQ purposes. But up tp you of course. |
|
| Back to top |
|
|
| MQAltaf |
| Posted: Thu Jun 02, 2005 6:09 am Post subject: |
|
|
Centurion
Joined: 10 Feb 2005
Posts: 119
|
| recycling as in stop/start queue manager. |
|
| Back to top |
|
|
| sebastianhirt |
| Posted: Thu Jun 02, 2005 6:20 am Post subject: |
|
|
Yatiri
Joined: 07 Jun 2004
Posts: 620
Location: Germany
|
| OK... But 99% sure the same thing. REFRESH SECURITY would have done also. |
|
| Back to top |
|
|
| anthony.barnes |
| Posted: Wed Jan 04, 2006 12:28 pm Post subject: |
|
|
Apprentice
Joined: 01 Jul 2003
Posts: 26
Location: Oak Brook, Illinois
|
| REFRESH SECURITY was just was I was looking for! Thanks for putting it out there. |
|
| Back to top |
|
|
| mqtypo |
| Posted: Thu Jan 05, 2006 1:20 am Post subject: |
|
|
Newbie
Joined: 07 Nov 2005
Posts: 5
|
It would have helped PD if you had said what you did, e.g.
I changed root to be part of the mqm group but I still get 2035 when trying to open a queue. |
|
| Back to top |
|
|
| anthony.barnes |
| Posted: Thu Jan 05, 2006 4:03 am Post subject: |
|
|
Apprentice
Joined: 01 Jul 2003
Posts: 26
Location: Oak Brook, Illinois
|
In my case I had added my qpasa user to my mqm group for remote administration of my Qmgr. Once that was done I was unable to access the Qmgr thru the QPasa GUI. I had the feeling that a Qmgr bounce may have cleared up the issue but due to a testing schedule that wasn't an option.
Seeing the "REFRESH SECURITY" command referenced by sebastianhirt was just want I needed to resolve my issue. |
|
| Back to top |
|
|
|
|
