Error Cc=2 Rc=2189 Cannot Put
Contents |
2030, 2033, 2035, 2080, 2085, 2092, 2110, 2189 2030 2033 2033 mqrc_no_msg_available 2035 2080 2085 2085 2092 2110 2189 2053 PremiumSupportTips mqrc 2035 Technote (troubleshooting) Problem(Abstract) WebSphere MQ program fails to process an MQ API call. MQ notifies
Mq Completion Code 2 Reason 2035
the program of the failure, by returning a completion code (MQCC), and a reason code (MQRC). These completion codes, and reason codes are documented in http://www.ibm.com/support/knowledgecenter/SSFKSJ_8.0.0/com.ibm.mq.tro.doc/q039210_.htm the WebSphere MQ Messages manual. Resolving the problem Completion codes The following is a list of the completion codes (MQCC) returned by WebSphere MQ. 0 Successful completion (MQCC_OK) 1 Warning (partial completion) (MQCC_WARNING) 2 Call failed (MQCC_FAILED) Reason codes For a list of reason codes, see Reason codes. You can http://www.ibm.com/support/docview.wss?uid=swg21167821 also use the MQRC utility program to display description of a reason code. Example: Details regarding the most common reason codes. This information is intended to document the most common causes for following reason codes. MQRC 2030 0x000007ee MQRC_MSG_TOO_BIG_FOR_Q MQRC 2033 0x000007f1 MQRC_NO_MSG_AVAILABLE MQRC 2035 0x000007f3 MQRC_NOT_AUTHORIZED MQRC 2080 0x00000820 MQRC_TRUNCATED_MSG_FAILED MQRC 2085 0x00000825 MQRC_UNKNOWN_OBJECT_NAME MQRC 2092 0x0000082c MQRC_XMIT_Q_USAGE_ERROR MQRC 2110 0x0000083e MQRC_FORMAT_ERROR MQRC 2189 0x0000088d MQRC_CLUSTER_RESOLUTION_ERROR Additional information For a list of reason codes, see Reason codes. For a list of feedback codes, see Feedback codes. Related information WebSphere MQ Recommended Fixes A Japanese translation is available Product Alias/Synonym WMQ MQ Document information More support for: WebSphere MQ Application / API Software version: 2.1.2, 3.0, 5.3.1, 6.0, 7.0, 7.0.1, 7.1, 7.5 Operating system(s): AIX, HP NonStop, HP-UX, IBM i, Linux, OpenVMS, Solaris, Windows, z/OS, z/VSE Reference #: 1167821 Modified date: 2006-03-14 Site availability Site assistance C
had put together for the developers. But it never occurred to me that they might be using qmgr name in the Open in this particular case. Yes, the application is probably using it, https://www.mail-archive.com/mqseries@akh-wien.ac.at/msg14002.html I was told. I cannot look at their code. I have been told that Smalltalk binding involves getting a Queue Manager connection, and passing that connection to the Open operation. Therefore QMAlias would not work (as they would http://www.codeproject.com/Articles/14009/Interfacing-with-IBM-WebSphere-MQ-formally-IBM-MQS have to connect to this QMAlias first, as part of their start-up proc in their ini file ). This will take them some time to investigate as the developer of the app is gone. I will post my mq error findings/resolution. Thanks again, Ruzi --- Neil Casey <[EMAIL PROTECTED]> wrote: > Hi Ruzi, > > check to see that the application MQOD which is > opened for output does not > contain a queue manager name. > > If the application puts the local queue manager name > (QM1 in your case) > into this field, it stops cluster name resolution > from working properly. Of > course the 'q' program and amqsputc don't do this, > mq error code so they will work. > > If your application forces a non-blank queue manager > name (at my site we > use Roma which enforces a non-blank QM name in MQOD > on MQOPEN), then you > can get around this by creating a dummy queue > manager alias. > > That is, you: > DEFINE QR(CLUSTER.QM) DESCR('Cluster QM Alias to map > to blank QM name') > (There are no other parameters required) > > on QM1. Your client app which specifies CLUSTER.QM > as the QM name on the Q > open will now resolve to a cluster queue as the QM > name is mapped by the > QMAlias to spaces. > > As an alternative to this, you can create the QR > (CLUSTER.QM) as a cluster > visible q on the QM(s) with the target queue. The > resolution will then go > via the alias, instead of resolving the queue name. > > Regards, > > Neil Casey. > > > |---------+----------------------------> > | | Ruzi R | > | | <[EMAIL PROTECTED]| > | | M> | > | | Sent by: MQSeries| > | | List | > | | <[EMAIL PROTECTED]| > | | n.AC.AT> | > | | | > | | | > | | 25/02/2004 09:43 | > | | Please respond to| > |
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... C# questions Linux questions ASP.NET questions SQL questions VB.NET 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 453.9K 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