Error 2058 Mq
Contents |
2058 2058 2058 2058 2058 2058 2058 2058 2058 2058 2058 2058 2058 2058 2058 2058 2058 2058 2058 2058 2058 2058 2058 mq error 2009 2058 2058 2058 2058 2058 2058 2058 2058 2058 2058 2058 2058 2058
Mqconn Reason Code 2058
MQRC Q MGR NAME ERROR queue manager name error reason return code 2058 MQRC Q MGR NAME ERROR
Mqje001 Completion Code '2' Reason '2058'
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 manager name error reason
Mqexception 2058
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 cause, however there can be other mq error 2045 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 the queue manager name is corrected, this works as expected. Example 3:
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker http://www.mqseries.net/phpBB2/viewtopic.php?p=291749&sid=7e7566fd9ac02b2728a241b6f51e5afc Support
MQSeries.net Forum Index » IBM MQ Java / JMS » got a 2058 reason code error accessing queues. Why??? got a 2058 reason code error accessing queues. Why??? « View previous topic :: View next topic » Author Message carlogol Posted: Tue May 13, 2003 12:03 am Post subject: got a 2058 reason code error mq error accessing queues. Why??? NewbieJoined: 17 Feb 2003Posts: 6 Hi all I am facing a strange problem. I have a java application which sends files (splitted into mq messages) to its counterpart via mq queues. More deeply: application A and B exchange files via mq. A sends B a file splitted into N mq messages to a particular queue (B-DATA QUEUE), and it also sends B a error 2058 mq particular mq message to another queue (say B-COMMAND QUEUE). B receives this command mq message and understands it has to "re-build" a file reading from its data queue. When the file has been rebuilt, B sends a proper message back to A using another queue (A-COMMAND QUEUE), saying that it successfully re-created the file. If A needs to send B a number of files, it does so by creating a number of threads (1 file - 1 thread). Every thread accesses the queue istantiating its own MQManager and MQQueues. OK: enough theory The problem is: I get a 2058 error (reason code) when the thread try to access the queue using this line of code: queue = manager.accessQueue( MQqueueName, qOpenOptions); The weird thing is that i do not always receive this error (actually: 99% of the times everything works fine) but (randomly?) only when many threads (say 50-60) are running. That's a mess! Please help me! Thanks in advance Carlo PS: please, forgive me for my bad English. If something is not clear enough... TELL ME Back to top fschofer Posted: Tue May 13, 2003 1:25 am Post subject: KnightJoined: 02 Jul 2001Posts: 522Location: Mainz, GermaRSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support
MQSeries.net Forum Index » IBM MQ API Support » 2058 MQRC_Q_MGR_NAME_ERROR with use of MQCHLTAB in C# Goto page Previous1, 2, 3, 4Next 2058 MQRC_Q_MGR_NAME_ERROR with use of MQCHLTAB in C# « View previous topic :: View next topic » Author Message pnicolay Posted: Fri Dec 03, 2010 2:14 am Post subject: ApprenticeJoined: 29 Nov 2010Posts: 26 No, I don't get the AMQ2058 anymore since I changed my new Queuemanager as follows... Code: connProps.Add(MQC.TRANSPORT_PROPERTY, MQC.TRANSPORT_MQSERIES_CLIENT); MQManager = new MQQueueManager("MYQM", connProps); Now the C# client locks up on the new Queuemanager statement. When using the amqsput/amqsputc I get the following... Code: C:\Program Files\IBM\WebSphere MQ\bin>amqsput MYTESTQ MYQM Sample AMQSPUT0 start MQCONN ended with reason code 2058 C:\Program Files\IBM\WebSphere MQ\bin>amqsputc MYTESTQ MYQM Sample AMQSPUT0 start (locks up) Back to top ramires Posted: Fri Dec 03, 2010 3:22 am Post subject: KnightJoined: 24 Jun 2001Posts: 505Location: Portugal - Lisboa with this: C:\Program Files\IBM\WebSphere MQ\bin>amqsput MYTESTQ MYQM Sample AMQSPUT0 start MQCONN ended with reason code 2058 you are trying to connect to a local queue manager MYQM and open a queue MYTESTQ. You don't have a queue manager MYQM on that box, so the 2058 is expected. To use the second option, amqsput client version, (amqsputc) you need an environment variable defining a channel to a queue manager, SET MQSERVER=something. Did you set MQSERVER? Back to top pnicolay Posted: Fri Dec 03, 2010 3:31 am Post subject: ApprenticeJoined: 29 Nov 2010Posts: 26 ramires wrote: To use the second option, amqsput client version, (amqsputc) you need an environment variable defining a channel to a queue manager, SET MQSERVER=something. Did you set MQSERVER? No, not MQSERVER... but MQCHLLIB and MQCHLTAB. Back to top ramires Posted: Fri Dec 03, 2010 3:34 am Post subject: KnightJoined: 24 Jun 2001Posts: 505Location: Portugal - Lisboa ok, thats also an option. Can you telnet to the qmgr host and port? Back to top pnicolay Posted: Fri Dec 03, 2010 3:42 am Post subject: ApprenticeJoined: 29 Nov 2010Posts: 26 As stated various times before... it works fine using MQEnvironment (for specifying all the required parameters), as well as from a Java client program... so there's nothing wrong with the queuemanager or configur