Mqopen Error 2035
Contents |
OOSETA MQOO_SET_ALL_CONTEXT mq400l2 Technote (troubleshooting) Problem(Abstract) When a
('mqcc_failed') Reason '2035' ('mqrc_not_authorized')
MQOPEN is issued against a queue on a remote mq error 2035 completion code 2 box, it receives reason code 2035, Not authorized. Cause Open options OOSETA (allow all context
Mqconn Ended With Reason Code 2035
to be set) and OOSAVA (save context) were being used on the MQOPEN. The WebSphere MQ for iSeries System Administration Guide states when mqrc_not_authorized c# using the MQOO_SET_ALL_CONTEXT on the MQOPEN or MQPUT1 apis, *SETALL authority is required for both the queue and the queue manager. Resolving the problem Grant the user issuing the MQOPEN *SETALL authority to both the local and remote queue managers and the remote queue. For example, The MQOPEN the call to initialize the user id failed with compcode 2 and reason 2035. is being performed against the queue MSGACP.MQSTDR.RTR.INPUT. This queue is on Queue Manager, TEST. The application doing the MQOPEN is running on Queue Manager, WBSTEST. The user profile this application is running under is called MQUSER. Give the MQUSER user profile *SETALL authority to the WBSTEST Queue Manager. GRTMQMAUT OBJ(WBSTEST) OBJTYPE(*MQM) USER(MQUSER) AUT(*SETALL) MQMNAME(WBSTEST) Give the MQUSER user profile *SETALL authority to the TEST Queue Manager. GRTMQMAUT OBJ(TEST) OBJTYPE(*MQM) USER(MQUSER) AUT(*SETALL) MQMNAME(TEST) Give the MQUSER user profile *SETALL authority to the MSGACP.MQSTDR.RTR.INPUT queue. GRTMQMAUT OBJ(MSGACP.MQSTDR.RTR.INPUT) OBJTYPE(*Q) USER(MQUSER) AUT(*SETALL) MQMNAME(TEST) Historical Number 78180082000 Document information More support for: WebSphere MQ Security Software version: 7.0.1, 7.1 Operating system(s): IBM i Reference #: 1163027 Modified date: 09 September 2004 Site availability Site assistance Contact and feedback Need support? Submit feedback to IBM Support 1-800-IBM-7378 (USA) Directory of worldwide contacts Contact Privacy Terms of use Accessibility
RSS
Mqopen Ended With Reason Code 2035
Feed - WebSphere MQ Support RSS Feed - Message Broker Support
MQSeries.net Forum mq disable channel authentication Index » IBM MQ API Support » MQOPEN fails with reason code 2035 Goto page 1, 2Next MQOPEN fails with reason code 2035 « ViewDspmqaut
previous topic :: View next topic » Author Message abajt Posted: Tue Jun 29, 2004 7:56 am Post subject: MQOPEN fails with reason code 2035 NewbieJoined: 01 May 2002Posts: 5 Hi, My app tries to http://www.ibm.com/support/docview.wss?uid=swg21163027 open a queue with open options MQOO_FAIL_IF_QUIESCING + MQOO_SET_ALL_CONTEXT + MQOO_OUTPUT, and fails with reason code 2035 despite the user has all the necessary authorities given to his group via setmqaut. I tried the same thing with the amqsput sample and get the same error : ./amqsput QTSWFANO QQEAIA1 10256 Sample AMQSPUT0 start target queue is QTSWFANO open options are 10256 MQOPEN ended with reason code 2035 unable to http://www.mqseries.net/phpBB/viewtopic.php?p=64884 open queue for output Sample AMQSPUT0 end 10256 = 0x2180 = MQOO_FAIL_IF_QUIESCING + MQOO_SET_ALL_CONTEXT + MQOO_OUTPUT The authorities on the queue are : browse get inq passall passid put set setall setid (= +allmqi) Even if I give all available (= +all) authorities to the group, I get same error. The amqsput sample works fine when executed under the mqm user. I use WMQ 5.3 / CSD6 under Sun Solaris 2.8 Is there something wrong ? André Back to top RogerLacroix Posted: Tue Jun 29, 2004 8:35 am Post subject: Jedi KnightJoined: 15 May 2001Posts: 2953Location: London, ON Canada Hi, After you changed / updated the security setting with the setmqaut command, did you issue the REFRESH SECURITY command (in runmqsc)? Do the dspmqaut command against the queue and group id and post the results here. Regards, Roger Lacroix Capitalware Inc._________________Capitalware: Transforming tomorrow into today. Connected to MQ! Twitter Back to top PeterPotkay Posted: Tue Jun 29, 2004 12:43 pm Post subject: Jedi CouncilJoined: 15 May 2001Posts: 7251Location: Hartford CT Andre, on UNIX, you need to run the setmqaut command against the group, not the individual ID._________________Peter Potkay Keep Calm and MQ On Back to top fjb_saper Posted: Tue Jun 29, 2004 1:46 pm Post subject:
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us http://stackoverflow.com/questions/5101840/error-2035-mqrc-not-authorized-while-connecting-to-mq Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack http://www.codeproject.com/Articles/14009/Interfacing-with-IBM-WebSphere-MQ-formally-IBM-MQS Overflow Community Stack Overflow is a community of 6.2 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Error '2035' ('MQRC_NOT_AUTHORIZED') While Connecting to MQ code 2 up vote 8 down vote favorite 2 I am getting this error while connecting to IBM MQ. I know that this is because of privileges, but is there any way just to check the connection with IBM MQ? Please suggest. asp.net websphere-mq share|improve this question edited Feb 26 '11 at 3:51 T.Rob 23.3k84381 asked Feb 24 '11 at 7:55 Sreenath G V 51124 add a comment| 5 ended with reason Answers 5 active oldest votes up vote 4 down vote You can also resolve this By setting mcauser('mqm') .. i was able to overcome 2035 error. Define channel (channel1) chltype (svrconn) trptype (tcp) mcauser(‘mqm’) Esp thanx to my SENIOR Bilal Ahmad (PSE) share|improve this answer edited Jun 18 '14 at 21:30 answered Mar 3 '14 at 10:58 Digital Alchemist 1,6551714 add a comment| up vote 2 down vote The 2035 suggests that your connection is getting to the QMgr. If you had the wrong channel name, host or port you would get back a 2059. The 2035 means that the connection made it to the listener, found a channel of the name that was requested and attempted a connection. If you want to test past this point it will be necessary to either authorize the ID that you are using to connect or to put an authorized ID in the MCAUSER attribute of the channel. For a detailed explanation of how the WMQ security works on client channels, see the WMQ Base Hardening presentation at http://t-rob.net/links. share|improve this answer answered Feb 26 '11 at 3:50 T.Rob 23.3k84381 add a comment| up vote 2 down vote If you enable authori
Articles Technical Blogs Posting/Update Guidelines Article Help Forum Article Competition Submit an article or tip Post your Blog quick answersQ&A Ask a Question about this article Ask a Question View Unanswered Questions View All Questions... Linux questions C# questions ASP.NET questions SQL questions fabric questions discussionsforums All Message Boards... Application Lifecycle> Running a Business Sales / Marketing Collaboration / Beta Testing Work Issues Design and Architecture ASP.NET JavaScript C / C++ / MFC> ATL / WTL / STL Managed C++/CLI C# Free Tools Objective-C and Swift Database Hardware & Devices> System Admin Hosting and Servers Java .NET Framework Android iOS Mobile SharePoint Silverlight / WPF Visual Basic Web Development Site Bugs / Suggestions Spam and Abuse Watch features Competitions News The Insider Newsletter The Daily Build Newsletter Newsletter archive Surveys Product Showcase Research Library CodeProject Stuff communitylounge Who's Who Most Valuable Professionals The Lounge  The Insider News The Weird & The Wonderful The Soapbox Press Releases Non-English Language > General Indian Topics General Chinese Topics help What is 'CodeProject'? General FAQ Ask a Question Bugs and Suggestions Article Help Forum Site Map Advertise with us About our Advertising Employment Opportunities About Us Articles » Platforms, Frameworks & Libraries » Cross Platform » General ArticleBrowse CodeStatsRevisionsAlternatives Comments (26) Add your ownalternative version Tagged as C#.NETWindowsVisual-StudioDev Stats 454.7K views62 bookmarked Posted 4 May 2006 Interfacing with IBM WebSphere MQ (formally IBM MQSeries) from .NET Khalid Al-Hadlaq, 4 May 2006 5.00 (15 votes) 1 2 3 4 5 5.00/5 - 15 votes2 removedμ 4.69, σa 1.27 [?] Rate this: Please Sign up or sign in to vote. This article is targeting architects and developers who are looking for a way to integrate .NET applications / Servers with IBM WebSphere MQ (IBM MQSeries). 1. Who should read this article? This article is targeting architects and developers who are looking for a way to integrate .NET applications / Servers with IBM WebSphere MQ (IBM MQSeries). 2. What to read? This article is designed to provide a basic understanding of messaging from IBM perspective through the explanation of some basic functionalities of WebSphere MQ. The document is divided into three main parts: a. Introduction to messaging: this is covered in sections 3 - 4.5. You can skip this part if you have a past experience with MSMQ. b. Interacting with WebSphere MQ: this is covered in sections 4.6 - 8,