Enable auth events, and try the test again. The msg on the event queue will contain the name of the object and the permissions required. The type of the msg will be the failing operation. _________________ MQSeries.net helps those who help themselves..
thanks for your reply. I am a bit late with my reaction but well, this issue had been put to lower priority.
Today I got back on the issue and solved it.
The problem was that the application responsible for picking up the message (so the COD could be sent out) was running as user a in group b. However in our /etc/group file the user a was not added to group b. Adding a to group b fixed it. So no real MQ issue, just a bad Solaris configuration.
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