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 » Unable to connect to the Remote QM's having '_ ' in its name

Post new topic  Reply to topic Goto page Previous  1, 2
 Unable to connect to the Remote QM's having '_ ' in its name « View previous topic :: View next topic » 
Author Message
exerk
PostPosted: Fri Oct 16, 2009 7:37 am    Post subject: Reply with quote

Jedi Council

Joined: 02 Nov 2006
Posts: 6339

Vitor wrote:
bruce2359 wrote:
Apps connect to qmgrs, not ports. The qmgr must have a listener (see DEFINE LISTENER or runmqlsr) running to receive the inbound attach request. You can use pretty much any port number you want.


Does WMQv5.3.7 have DEFINE LISTENER? I thought that came in with v6.


It did, but the QB manual stated that use of inetd and /etc/services was deprecated, and that runmqlsr should be used. That said, at my current site it was left in when the migration to V5.3 occurred - no validity review was carried out (not unusual I suspect).
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys.
Back to top
View user's profile Send private message
Vitor
PostPosted: Fri Oct 16, 2009 8:33 am    Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

exerk wrote:
It did, but the QB manual stated that use of inetd and /etc/services was deprecated, and that runmqlsr should be used. That said, at my current site it was left in when the migration to V5.3 occurred - no validity review was carried out (not unusual I suspect).


I know all that, and I got left with a lot of inetd as well on the "leave well enough alone" principle.

My point is that I though below v6 you had to explicitly use runmqlsr; you couldn't administer it via runmqsc because it wasn't a queue manager object at that level.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
exerk
PostPosted: Fri Oct 16, 2009 8:37 am    Post subject: Reply with quote

Jedi Council

Joined: 02 Nov 2006
Posts: 6339

Vitor wrote:
...My point is that I though below v6 you had to explicitly use runmqlsr; you couldn't administer it via runmqsc because it wasn't a queue manager object at that level.


My misinterpretation, apologies and correct - it required explicit usage of runmqlsr.
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys.
Back to top
View user's profile Send private message
satya_jammy
PostPosted: Fri Oct 16, 2009 9:41 am    Post subject: Reply with quote

Acolyte

Joined: 01 Oct 2009
Posts: 66

i am not asking how to create listner and assign a port to it. what i am asking is after creating a Qmanager and running the listner using runmqlsr for the portt 4444. what entries i ned to make in /etc/services so that the outside apps can connect to QM using listner.
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Fri Oct 16, 2009 10:41 am    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20767
Location: LI,NY

satya_jammy wrote:
i am not asking how to create listner and assign a port to it. what i am asking is after creating a Qmanager and running the listner using runmqlsr for the portt 4444. what entries i ned to make in /etc/services so that the outside apps can connect to QM using listner.

Absolutely none. But you have to make sure that runmqlsr is running under an ID that has authorization to the qmgr and queues. Otherwise you might be in for quite some surprises...
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
satya_jammy
PostPosted: Sat Oct 17, 2009 4:03 am    Post subject: Reply with quote

Acolyte

Joined: 01 Oct 2009
Posts: 66

[quote="Vitor" Don't play with /etc/services in v5.3.7 - use runmqlsr..[/quote]


i found an entry for all the ports in /etc/services for the QM's using runmqlsr for listner..
do u mean their is no need of any entries in /etc/services.. if i use runmqlsr?
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Sat Oct 17, 2009 4:52 am    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20767
Location: LI,NY

satya_jammy wrote:
[quote="Vitor" Don't play with /etc/services in v5.3.7 - use runmqlsr..


i found an entry for all the ports in /etc/services for the QM's using runmqlsr for listner..
do u mean their is no need of any entries in /etc/services.. if i use runmqlsr?[/quote]


It's a good practice because then you know which ports are "reserved" for MQ.
However it is no longer a need with runmqlsr...
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
Display posts from previous:   
Post new topic  Reply to topic Goto page Previous  1, 2 Page 2 of 2

MQSeries.net Forum Index » General IBM MQ Support » Unable to connect to the Remote QM's having '_ ' in its name
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.