Amqsputc Error 2058
Contents |
2058 2058 2058 2058 2058 2058 2058 2058 2058 2058 2058 2058 2058 2058 2058 2058 2058 2058 2058 2058 2058
Mq Completion Code 2 Reason 2058
2058 2058 2058 2058 2058 2058 2058 2058 2058 2058 2058 2058 mq error 2085 2058 2058 2058 MQRC Q MGR NAME ERROR queue manager name error reason return code 2058 MQRC Q mqconn ended with reason code 2058 amqsputc MGR NAME ERROR queue manager name error reason return code 2058 MQRC Q MGR NAME ERROR queue manager name error reason return code 2058 MQRC Q MGR NAME ERROR queue
Mqrc_q_mgr_name_error
manager name error reason return code 2058 MQRC Q MGR NAME ERROR queue manager name error reason return code Technote (troubleshooting) Problem(Abstract) Your program attempts to connect to WebSphere MQ and fails. Symptom 2058 0x0000080a MQRC Q MGR NAME ERROR Cause 2058 is returned when connecting to a queue manager using the wrong queue manager name. This is the most common
Mq Error 2035
cause, however there can be other reasons for this failure. Resolving the problem Ensure that the queue manager name is specified correctly on: MQCONN API calls QREMOTE object definitions Client connection channel definitions Debugging QCF, TCF, or Client connection problems are much more complex. Ensure that the connection request is routed to the intended machine and queue manager. Verify that the listener program is starting the channel on the correct queue manager. Ensure that the specifications for the client environment variables are correct. mqserver mqchllib mqchltab If you are using a client channel table (amqclchl.tab), then verify that your client connection channel definition has the correct queue manager name (QMNAME) specified. Corrective actions: Specify the correct queue manager name. Correct channel routing problems. Correct inetd listener configuration problems. Correct client related configuration problems. Example 1: In this example, the sample program (amqsput) is used to put a message to queue (SVR.LQ) on queue manager (svr). Notice that it fails with reason code 2058. This failure occurs because the queue manager name is "SVR", not "svr". Example 2: After th
RSS Feed - WebSphere MQ Support RSS Feed mqconn ended with reason code 2538 - Message Broker Support
MQSeries.net Forum Index » General Discussion » amqsput works fine, amqsputc fails with errorWebsphere Mq Call Failed With Compcode '2' ('mqcc_failed') Reason '2058' ('mqrc_q_mgr_name_error')
2058 amqsput works fine, amqsputc fails with error 2058 « View previous topic :: View next topic » Author Message sameer Posted: Wed May mqconn ended with reason code 2059 10, 2006 10:12 am Post subject: amqsput works fine, amqsputc fails with error 2058 NoviceJoined: 09 Sep 2004Posts: 12Location: NY I have a Linux MQ series setup, I can put a message fine using amqsput, but, with amqsputc, http://www.ibm.com/support/docview.wss?uid=swg21166938 I get 2085 error for the same queue. Appreciate any ideas that can help me resolve this issue Sameer ______________________________ -bash-2.05b$ ./amqsput TESTQ Sample AMQSPUT0 start target queue is TESTQ test Sample AMQSPUT0 end -bash-2.05b$ ./amqsputc TESTQ Sample AMQSPUT0 start MQCONN ended with reason code 2058 Back to top vennela Posted: Wed May 10, 2006 10:14 am Post subject: Jedi KnightJoined: 11 Aug 2002Posts: 4054Location: Hyderabad, India It is not 2085, it is 2058 Have you http://www.mqseries.net/phpBB/viewtopic.php?t=29385&sid=6d0ac4ca6c50af83f05100b134ec6f61 set MQSERVER variable Back to top Toronto_MQ Posted: Wed May 10, 2006 10:21 am Post subject: MasterJoined: 10 Jul 2002Posts: 263Location: read my name Have you set the MQSERVER variable? Or are you using a client channel table? If the answer to both of these is 'no', then may I suggest you search the forums for amqsputc. Lots of information for you in there. Back to top sameer Posted: Wed May 10, 2006 10:48 am Post subject: amqsput works fine, amqsputc fails with error 2058 NoviceJoined: 09 Sep 2004Posts: 12Location: NY Thanks for the reply. I have setup export MQServer='SYSTEM.DEF.SVRCONN/TCP/Box IP(1414)' and yet I get the error. Appreciate your help. Back to top jefflowrey Posted: Wed May 10, 2006 10:56 am Post subject: Grand PoobahJoined: 16 Oct 2002Posts: 19981 Please search this website for "2058", to see all the other examples of how to troubleshoot this process. Follow those examples, and document your results. Then, if you still have a problem, come back and post again and explain what you have tried and what the results were, and whether or not you are still getting the same error._________________I am *not* the model of the modern major general. Back to top Toronto_MQ Posted: Wed May 10, 2006 11:13 am Post subject: MasterJoined: 10 Jul 2002Posts: 263Location: read my name Here's a hint, or at least a st
in the MQCONN, you get 2058. In scenario 2, there is no matching CLNTCONN channel based on the QMname parameter in the MQCONN, https://www.mail-archive.com/mqseries@akh-wien.ac.at/msg06978.html you get 2059. Why the diff? I would think you should get the same error for both, and probably the 2059 based on the below excerpts from the manual. MQRC_Q_MGR_NAME_ERROR (2058) Explanation: On https://www.experts-exchange.com/questions/21863362/HELP-MQ-Series-error-when-using-sample-'amqsput'-reason-code-2035.html an MQCONN or MQCONNX call, the value specified for the QMgrName parameter is not valid or not known. MQRC_Q_MGR_NOT_AVAILABLE (2059) Explanation: On an MQCONN or MQCONNX call, the queue manager identified by code 2 the QMgrName parameter is not available for connection. This reason code can also occur if the call is issued by an MQ client application and there is an error with the client-connection or the corresponding server-connection channel definitions. Peter Potkay IBM MQSeries Certified [EMAIL PROTECTED] X 77906 -----Original Message----- From: Peter Uranyi [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 04, 2003 2:08 PM To: [EMAIL PROTECTED] mqconn ended with Subject: Re: CLNTCONN - mqrc 2058 error If you define your client channel like this: DEFINE CHANNEL(OH4848T1.SVRCONN) + CHLTYPE(CLNTCONN) + CONNAME('hostname(port)') Then: "amqsputc QL.TEST" will work, but "amqsputc QL.TEST OH4848T1" will return 2058 (MQRC_Q_MGR_NAME_ERROR) That's because you specified the qmgr name in your program, so mq will look for an entry in the channel table with this name. If you define the qmgr name when you create your client channel: DEFINE CHANNEL(OH4848T1.SVRCONN) + CHLTYPE(CLNTCONN) + CONNAME('hostname(port)') + QMNAME(OH4848T1) Then: "amqsputc QL.TEST" will return 2059 (MQRC_Q_MGR_NOT_AVAILABLE) "amqsputc QL.TEST OH4848T1" will work. Now the first command will fail because you didn't specify the qmgr in the program, so mq will look for an entry in the channel table with a blank qmgr name. If you want to have it to work both ways, you have to create two channels, one with a qmgr name and one without. --- "Yeh, Jeff" <[EMAIL PROTECTED]> wrote: > We have Windows 2000 Advanced Servers. > I am having a strange problem of using client connection. > I have environmental variables properly defined for MQCHLLIB and MQCHLTAB > in Client machine. > In server machine, the queue manager, I
Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Expand Search Submit Close Search Login Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > HELP! MQ Series error when using sample 'amqsput' - reason code 2035 Want to Advertise Here? Solved HELP! MQ Series error when using sample 'amqsput' - reason code 2035 Posted on 2006-05-25 Java App Servers 1 Verified Solution 3 Comments 19,132 Views Last Modified: 2013-12-10 I'm trying to establish exactly why my UNIX user (t20ora) can't "put" messages on and "get" messages from the test queue, (as provided by the MQ Series install), but am up against a brick wall! My UNIX Environment: - Solaris version: SunOS sauron 5.9 Generic_118558-02 sun4u sparc SUNW,Ultra-4 - Websphere MQ Series v5.3 (installed from 'C44J8ML.tar.Z', downloaded directly from IBM's website) -------------------------------------------------------------------------------- Actions undertaken: Running the test 'put' and 'get' from the designated queue: Trying to put & get a test message to the designated queue gives the following problem.... -------------------------------------------------------------------------------- ################################################## - As mqm user (the user whom MQ Series was installed as) sauron:mqm >cd /opt/mqm/samp/bin/ sauron:mqm >./amqsput INPUT_OUTPUT_Q Sample AMQSPUT0 start target queue is INPUT_OUTPUT_Q test message Sample AMQSPUT0 end sauron:mqm >./amqsget INPUT_OUTPUT_Q Sample AMQSGET0 start message