ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » General IBM MQ Support » setmqaut - 2035

Post new topic  Reply to topic
 setmqaut - 2035 « View previous topic :: View next topic » 
Author Message
mqmike
PostPosted: Mon Nov 15, 2004 4:54 am    Post subject: setmqaut - 2035 Reply with quote

Acolyte

Joined: 09 Jul 2004
Posts: 63

We are having some problems with our application receiving a 2035. The queue it is attempting to put to is a dynamic reply queue that. I have given the model queue that it is using +all authority but we are still getting the same error.

Could someone please help?
Back to top
View user's profile Send private message
PeterPotkay
PostPosted: Mon Nov 15, 2004 4:59 am    Post subject: Reply with quote

Poobah

Joined: 15 May 2001
Posts: 7722

Did you give the ID in question access to connect to the Queue Manager?

Code:

setmqaut -m YourQueueManagerName -t qmgr -p TheUserIDinQuestion +allmqi

_________________
Peter Potkay
Keep Calm and MQ On
Back to top
View user's profile Send private message
mqmike
PostPosted: Mon Nov 15, 2004 5:05 am    Post subject: Reply with quote

Acolyte

Joined: 09 Jul 2004
Posts: 63

Peter - thanks for your quick response!

The qmgr has +connect permission. Anything else required?

I'm guessing the qmgr alias doesn't need anything special?
Back to top
View user's profile Send private message
PeterPotkay
PostPosted: Mon Nov 15, 2004 5:17 am    Post subject: Reply with quote

Poobah

Joined: 15 May 2001
Posts: 7722

dspmqauts for the UserID in question and the MQ objects in question would help. As would an indication exactly where you are getting the 2035.

Anywho, without knowing what your program is doing, it is possible +connect is not enough. You may need +inq and/or +altusr.
_________________
Peter Potkay
Keep Calm and MQ On
Back to top
View user's profile Send private message
mqmike
PostPosted: Mon Nov 15, 2004 5:57 am    Post subject: Reply with quote

Acolyte

Joined: 09 Jul 2004
Posts: 63

thanks peter

ive sorted this now - the x-mitq didnt have the right auth
Back to top
View user's profile Send private message
Nigelg
PostPosted: Mon Nov 15, 2004 6:00 am    Post subject: Reply with quote

Grand Master

Joined: 02 Aug 2004
Posts: 1046

If this is on Windows, the qmgr error log has an error msg which details the missing authority.
On UNIX, a qmgr auth event msg is generated in the SYSTEM.ADMIN.QMGR.EVENT queue if the qmgr attribute AUTHOREV is set to ENABLED. This will tell you the missing authorities (possibly) on an MQCONN, MQOPEN, MQPUT1 or MQCLOSE. It will not help for an MQPUT. See the WMQ Event Monitoring manual for details of the 4 types of authority event msgs.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » General IBM MQ Support » setmqaut - 2035
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.