| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| AMQ4036 on MQ6 on Linux |
« View previous topic :: View next topic » |
| Author |
Message
|
| chrisc |
 Posted: Tue Jul 15, 2008 5:31 pm Post subject: AMQ4036 on MQ6 on Linux |
 |
|
Voyager
Joined: 19 Mar 2006
Posts: 77
|
I know this topic has been asked about many times before, but I have gone through the solutions in other posts and they don't seem to resolve it for me.
We are running MQ 6.0.2 on Linux and are trying to lock down the security on a couple of new queue managers. However, when I try to apply the security, it is so effective that I can't connect using MQ Explorer, even though - theoretically - I have granted it access to connect.
The SYSTEM.ADMIN.SVRCONN channel has an MCAUSER of 'mqxpl' for MQ Explorer access.
The SYSTEM.DEF.SVRCONN channel has an MCAUSER of 'mqmon' for a monitoring process that is run here. I'll ignore this one for the rest of this post.
In /etc/group I have an entry to create an MQ explorer group:
In /etc/passwd I have the mqxpl user itself, assigned to the corresponding group:
| Code: |
| mqxpl::500:501::/home/mqxpl:/bin/bash |
I then run the following:
| Code: |
setmqaut -m QM1 -t qmgr -g mqxplg +connect +inq +dsp
setmqaut -m QM1 -n SYSTEM.ADMIN.COMMAND.QUEUE -t q -g mqxplg +put +inq +dsp
setmqaut -m QM1 -n SYSTEM.DEFAULT.MODEL.QUEUE -t q -g mqxplg +get +browse +inq +dsp |
Then for each queue I do +browse +dsp +inq, and each namelist and process gets +dsp +inq.
After all this I do a REFRESH SECURITY in runmqsc, plus I've tried restarting the queue managers etc etc etc.
Despite all this I still get the AMQ4036 Not Authorised error when I try to connect using MQExplorer. Any ideas what I'm doing wrong? This is driving me up the wall in frustration.
(P.S. As soon as I change the MCAUSER to 'mqm', it all works - obviously - so I know the queue manager itself is not having problems... it's all down to the security I'm trying to apply.)
Any help would be greatly appreciated!
Thanks,
Chris |
|
| Back to top |
|
 |
| veech23 |
| Posted: Tue Jul 15, 2008 8:32 pm Post subject: |
|
|
Novice
Joined: 25 Apr 2007
Posts: 23
Location: canberra
|
|
| Back to top |
|
|
| chrisc |
| Posted: Tue Jul 15, 2008 9:46 pm Post subject: |
|
|
Voyager
Joined: 19 Mar 2006
Posts: 77
|
Ah, many thanks for that. It seems to have been those additional queues that were the issue. I can now connect with no problems.
The only thing is, although I can connect, when I want to view channels or queues or anything the progress bar does its little "in progress" animation but nothing ever shows up in the view.
If I right-click on the Queues folder and ask to view the current status, the queues are all listed there, but the normal view is empty. This is even when I have the "Show System Objects" button pressed. I have done the setmqaut on all the queues and channels, giving them +dsp access.
Is this a side effect of not being MQM, or is there something else I am doing wrong?
Thanks,
Chris |
|
| Back to top |
|
|
| chrisc |
| Posted: Tue Jul 15, 2008 10:34 pm Post subject: |
|
|
Voyager
Joined: 19 Mar 2006
Posts: 77
|
Never mind, I think I found the answer - the MQ Explorer is running on MQ v6.0.0.0. There is apparently a known problem with this that prevents queues being viewable this way: http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg1IC49051.
(I should have read the rest of the other article, it talked about the problem there.)
Thanks for your help veech.
Chris |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
