ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » General IBM MQ Support » MQRC_Q_MGR_NAME_ERROR (2058) connecting to running qmgr.

Post new topic  Reply to topic
 MQRC_Q_MGR_NAME_ERROR (2058) connecting to running qmgr. « View previous topic :: View next topic » 
Author Message
aboggis
PostPosted: Fri Sep 12, 2003 9:05 am    Post subject: MQRC_Q_MGR_NAME_ERROR (2058) connecting to running qmgr. Reply with quote

Centurion

Joined: 18 Dec 2001
Posts: 105
Location: Auburn, California

I am at a loss to explain the following... (Solaris 5.8, WMQ 5.2 CSD06):

Code:

$ dspmq
QMNAME(CLUSTER2B.AR1.MANAGER)     STATUS(Running)
.
.
$ export MQSERVER=SYSTEM.ADMIN.SVRCONN/tcp/127.0.0.1\(1414\)
$ /opt/mqm/samp/bin/amqsputc SYSTEM.DEFAULT.LOCAL.QUEUE CLUSTER2B.AR1.MANAGER
Sample AMQSPUT0 start
MQCONN ended with reason code 2058
$


I also tried the same from a Windows client and get the same error.
I also tried using SYSTEM.DEF.SVRCONN - same error. I am having the same problem on all my queue managers.

The only errors I have in my logs are cluster channel errors: 'AMQ9558: Remote Channel is not currently available.'.

I am reluncant to simply restart the queue managers, but I'm at a loss to explain.

tonyB.
Back to top
View user's profile Send private message AIM Address Yahoo Messenger
GMcCarthy
PostPosted: Fri Sep 12, 2003 9:59 am    Post subject: Reply with quote

Centurion

Joined: 06 Nov 2001
Posts: 113
Location: Melville NY

I have a few questions as I am not all that familiar with Solaris:

1) are the extra '\' in your MQSERVER variable supposed to be there?

Shouldn't it read:

export MQSERVER=SYSTEM.ADMIN.SVRCONN/tcp/127.0.0.1(1414)

2) Is the listener running on your server for port 1414?
_________________
Regards,
Gina

IBM Certified MQSeries Specialist
Back to top
View user's profile Send private message Visit poster's website AIM Address Yahoo Messenger
bower5932
PostPosted: Fri Sep 12, 2003 10:03 am    Post subject: Reply with quote

Jedi Knight

Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA

I also believe that the tcp has to be in upper case in your environment variable on Solaris.
Back to top
View user's profile Send private message Send e-mail Visit poster's website AIM Address Yahoo Messenger
GMcCarthy
PostPosted: Fri Sep 12, 2003 10:14 am    Post subject: Reply with quote

Centurion

Joined: 06 Nov 2001
Posts: 113
Location: Melville NY

YES! TCP needs to be in upper case on all platforms, from what I can see in the clients manual. Also, you may have to put the address and port in single queues.

export MQSERVER=SYSTEM.ADMIN.SVRCONN/TCP/'127.0.0.1(1414)'


Another thing to be aware of is security. You may need an MCA USER ID defined on the server connection definition.
_________________
Regards,
Gina

IBM Certified MQSeries Specialist
Back to top
View user's profile Send private message Visit poster's website AIM Address Yahoo Messenger
aboggis
PostPosted: Fri Sep 12, 2003 10:15 am    Post subject: Reply with quote

Centurion

Joined: 18 Dec 2001
Posts: 105
Location: Auburn, California

I think, after further troubleshooting, what I have here is a local network issue.

After a comment on using amqsput (and it working) and the reminder that Solaris is case sensitive ('TCP' is ok, 'tcp' is not) I retried using ampsputc and was able to put messages (as a client) to all the queue managers in my cluster.

So, I retried the same from my Windows workstation. No joy, still get 2058 errors, regardless of 'tcp or 'TCP' in the MQSERVER environment. As Paul says, it shouldn't matter on Windows, since it's case-insensitive.

So, I tried the Websphere MQ Explorer MMC and I can now connect to all the qmgrs in my cluster. Going back to a fresh command prompt... everything now works.

Looks like I'll be having a conversation with our networking guys...

Thanks for all your pointers.

To 'GMcCarthy' : The '\' is there for Solaris because the '(' is a special character that is interpreted by the [bash] shell. Using the '\' character before it 'escapes' the '(' so that it is interpreted correctly.

tonyB.
Back to top
View user's profile Send private message AIM Address Yahoo Messenger
GMcCarthy
PostPosted: Fri Sep 12, 2003 10:18 am    Post subject: Reply with quote

Centurion

Joined: 06 Nov 2001
Posts: 113
Location: Melville NY

Thanks for the '\' explanation.
_________________
Regards,
Gina

IBM Certified MQSeries Specialist
Back to top
View user's profile Send private message Visit poster's website AIM Address Yahoo Messenger
Leafar
PostPosted: Fri Sep 12, 2003 10:24 am    Post subject: Reply with quote

Acolyte

Joined: 03 Apr 2003
Posts: 74
Location: Buenos Aires

Is the runmqcsv running in solaris???
Back to top
View user's profile Send private message MSN Messenger
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » General IBM MQ Support » MQRC_Q_MGR_NAME_ERROR (2058) connecting to running qmgr.
Jump to:  



You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.