Ibm Websphere Mq Error 2058
Contents |
2058 2058 2058 2058 2058 2058 2058 2058 2058 2058 2058 2058 2058 2058 2058 2058 2058 2058 2058 2058 2058 2058 2058 2058 2058 2058 2058 2058 2058 2058 2058 2058 2058 2058 2058 mqconn ended with reason code 2058 2058 MQRC Q MGR NAME ERROR queue manager name error reason return code 2058
Mqrc_q_mgr_name_error 2058
MQRC Q MGR NAME ERROR queue manager name error reason return code 2058 MQRC Q MGR NAME ERROR queue manager name error reason mqconn ended with reason code 2538 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 return code Technote (troubleshooting) Problem(Abstract) Your program attempts to connect
Mq 2059
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 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 mqconnx ended with reason code 2058 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: In this example the mqserver environment variable is used to configure a channel connection, from the client to the server, using channel(SYSTEM.DEF.SVRCONN). The client program (amqsputc) attempts to connect to queue manager(SVR), and to put a message to queue(SVR.LQ). This program fails with MQRC 2058, because queue manager(SVR) is not listening on port(1414); queue manager(HOBSON) was listening on port(1414). Example 4: After the mqserver is changed to include the cor
code 2058? 2 replies Latest Post - 2014-01-16T23:01:07Z by mbezite Display:ConversationsBy Date 1-3 of 3 Previous Next mbezite 060001HNXK 2 Posts Pinned topic MQCONN ended with reason code 2058? 2014-01-16T19:39:28Z | Tags: Answered
Mq Error 2085
question This question has been answered. Unanswered question This question has not
Mq Error 2035
been answered yet. I created a cluster with two full repositories queue managers and started them successfully. Each of amqsputc 2058 the queue manager can see the queues on the cluster but am getting "MQCONN ended with reason code 2058" when I try to put or get a message to a queue http://www.ibm.com/support/docview.wss?uid=swg21166938 created on another queue manager. Please advice. WMQ = 7.5 OS = RedHat command whereTESTWMBQ is the name of the queue created on the other queue manager QMB bash-4.1$ ./amqsget TESTWMBQ QMB Sample AMQSGET0 start MQCONN ended with reason code 2058 This shows both queue managers are in the same cluster: [mqm@TTRH-vWMQ75-2 bin]$ echo 'display clusqmgr(*) qmtype status' |/opt/mqm/bin/runmqsc QMB 5724-H72 https://www.ibm.com/developerworks/community/forums/html/topic?id=d1afd166-d704-4908-812e-3799ba61f16c (C) Copyright IBM Corp. 1994, 2011. ALL RIGHTS RESERVED. Starting MQSC for queue manager QMB. 1 : display clusqmgr(*) qmtype status AMQ8441: Display Cluster Queue Manager details. CLUSQMGR(QMA) CHANNEL(CHANNEL.QMA) CLUSTER(CLUSTER1) QMTYPE(REPOS) STATUS(RUNNING) AMQ8441: Display Cluster Queue Manager details. CLUSQMGR(QMB) CHANNEL(CHANNEL.QMB) CLUSTER(CLUSTER1) QMTYPE(REPOS) STATUS(RUNNING) One MQSC command read. No commands have a syntax error. All valid MQSC commands were processed. And the queue is visible in the cluster: AMQ8409: Display Queue details. QUEUE(TESTWMBQ) TYPE(QCLUSTER) One MQSC command read. No commands have a syntax error. All valid MQSC commands were processed. Log in to reply. GBaddeley 270005X5J1 302 Posts ACCEPTED ANSWER Re: MQCONN ended with reason code
CALL IF THE MQSERVER VARIABLE HAS BEEN CHANGED. Fixes are available WebSphere MQ V7.0 Fix Pack 7.0.1.2 WebSphere http://www.ibm.com/support/docview.wss?uid=swg1IC63166 MQ V7.0.1 for i5/OS Fix Pack 7.0.1.2 Subscribe You can track all active APARs for this component. APAR status Closed as program error. Error description A client application connecting to a server using MQSERVER environment variable, gets 2058(MQRC_Q_MGR_NAME_ERROR) from MQCONN. This is because of a change in MQ v7 that led to the cached value of MQSERVER mq error being used during the MQCONN call. In MQ V6, this caching mechanism was not present and hence it could pick up the latest MQSERVER variable at each MQCONN. Local fix Problem summary **************************************************************** USERS AFFECTED: WebSphere MQ client users where, 1. Application disconnects from one queue manager and tries to reconnect to different queue manager on different host. ended with reason 2. MQSERVER environment variable is used in the application. Platforms affected: All Distributed (iSeries, all Unix and Windows) **************************************************************** PROBLEM SUMMARY: When the client application connects to a server using MQSERVER environment variable, WebSphere MQ caches the value in the ServerConnectionParms attribute. This cached value will be used, when the application tries to reconnect to a different queue manager on a different server instead of the new MQSERVER variable. Since the new value is not used during connection, the client application gets 2058(MQRC_Q_MGR_NAME_ERROR) error during MQCONN. Problem conclusion WebSphere MQ code has been modified such that during each MQCONN, the newly specified MQSERVER value is used in connecting to the queue manager. --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: v7.0 Platform Fix Pack 7.0.1.2 -------- -------------------- Windows U200316 AIX U829807 HP-UX (PA-RISC) U829678 HP-UX (Itanium) U829681 Solaris (SPARC) U829806 Solaris (x86-64) U829680 iSeries tbc_p700_0_1_2 Linux (x86) U829677 Linux (x86-64) U829676 Linux (zSeries) U829682 Linux (Power) U829679 The latest available maintenance can be obtained from 'WebSphere MQ Recommended Fixes'