| Author |
Message
|
| mqmblife |
 Posted: Fri Sep 09, 2011 1:17 am Post subject: Unable to view Port number of a queue manager |
 |
|
Novice
Joined: 24 Aug 2011
Posts: 21
|
Hi All,
I want to know the port number of a queue manager to add it to my MQ Explorer. I tried all the below commands but no use, can anyone please let me know to get out of this. That would be a great help!!
DISPLAY LISTENER(*)
ps -ef|grep runmqlsr
ps -ef|grep QMGR NAME
netstat
runmqlsr
Regards,
Venkat |
|
| Back to top |
|
 |
| bruce2359 |
| Posted: Fri Sep 09, 2011 2:25 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
Does the qmgr have operating channels of any kind currently? If not, it will likely not have a running listener.
What was the result of your attempt to execute DISPLAY LISTENER(*) command? Paste the output here.
What was the result of your attempt to execute ps -ef|grep runmqlsr command?
What was the result of your attempt to execute ps -ef|grep QMGR NAME command?
What was the result of your attempt to execute netstat command?
What was the result of your attempt to execute runmqlsr command?
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| mqmblife |
| Posted: Fri Sep 09, 2011 3:17 am Post subject: |
|
|
Novice
Joined: 24 Aug 2011
Posts: 21
|
| bruce2359 wrote: |
Does the qmgr have operating channels of any kind currently? If not, it will likely not have a running listener.
What was the result of your attempt to execute DISPLAY LISTENER(*) command? Paste the output here.
AMQ8630: Display listener information details.
LISTENER(SYSTEM.DEFAULT.LISTENER.TCP)
What was the result of your attempt to execute ps -ef|grep runmqlsr command?
xxxxx 6115356 2212016 0 07:07:03 pts/1 0:00 grep runmqlsr
What was the result of your attempt to execute ps -ef|grep QMGR NAME command?
aaaa 450600 6430766 0 Jun 27 - 0:51 amqzlaa0 -mXXXX -fip2
aaaa 655592 6430766 0 Sep 07 - 0:00 amqzlaa0 -mXXX -fip15
aaaa 757940 1802322 0 Jun 27 - 0:49 /usr/mqm/bin/amqpcsea XXXX
aaaa 979114 1802322 0 Jun 27 - 0:50 /usr/mqm/bin/runmqchi -m XXXX -q SYSTEM.CHANNEL.INITQ -r
aaaa 1265690 6430766 0 Jun 27 - 33:43 amqzlaa0 -mXXXX -fip0
aaaa 1421338 6430766 0 Jun 27 - 0:57 amqzmuf0 -m XXX
aaaa 1437752 6430766 0 Jun 27 - 0:31 /usr/mqm/bin/amqrrmfa -m XX -t2332800 -s2592000 -p2592000 -g5184000 -c3600
aaaa 1441854 6430766 0 Jun 27 - 1:14 /usr/mqm/bin/amqzdmaa -m XXXX
aaaa 1802322 6430766 0 Jun 27 - 0:29 /usr/mqm/bin/amqzmgr0 -m XXXX
aaaa 6078612 6430766 0 Jun 27 - 1:12 amqzmuc0 -m XXX
aaaa 6115416 2212016 0 07:07:49 pts/1 0:00 grep XXXX
mqm 6135924 233494 0 Jun 28 - 1:52 amqcrsta -m XXX
aaaa 6340726 6430766 0 Jun 27 - 0:47 /usr/mqm/bin/amqzfuma -m XXXX
mqm 6426850 233494 0 Sep 07 - 0:03 amqcrsta -m XXX
aaaa 6430766 1 0 Jun 27 - 2:08 amqzxma0 -m XXX
mqm 6479988 233494 0 Jun 27 - 2:45 amqcrsta -m XXX
aaaa 6488292 6430766 0 Jun 27 - 2:34 amqzmur0 -m XXX
What was the result of your attempt to execute netstat command?
What was the result of your attempt to execute runmqlsr -m qmgr name -t TCP command? |
09/09/11 07:12:55 AMQ9218: The TCP/IP listener program could not bind to port number 1414. |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Sep 09, 2011 4:12 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| mqmblife wrote: |
| bruce2359 wrote: |
What was the result of your attempt to execute DISPLAY LISTENER(*) command? Paste the output here.
| Code: |
AMQ8630: Display listener information details.
LISTENER(SYSTEM.DEFAULT.LISTENER.TCP) |
|
|
This queue mamanger (unless it's an unfeasibly old release) is not defined to use a port. If it's a release that old, it should have responded to the DISPLAY LISTENER command with "What?".
What makes you think it does have one (e.g. it has running channels as my worthy associate comments above)?
Is this queue manager in active use in any respect or is it something that's just been defined? Possibly on your local machine?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mqmblife |
| Posted: Fri Sep 09, 2011 6:30 am Post subject: |
|
|
Novice
Joined: 24 Aug 2011
Posts: 21
|
Yes this queue manager is up and running and it is used in one of our test instances. And coming to port number I have come to know from my colleague that it is 1420. And I tried adding it to my MQ Explorer, it worked. But I want to see where it is defined.
Regards
Venkat |
|
| Back to top |
|
|
| exerk |
| Posted: Fri Sep 09, 2011 6:42 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
Check etc/services, check inetd, and if that's where it's set remove the entries, then define and configure a Listener object.
_________________
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 |
|
|
| Vitor |
| Posted: Fri Sep 09, 2011 6:46 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| exerk wrote: |
| define and configure a Listener object. |
Even if it's not an unfeasibilty old version it's using an unfeasibly old method.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Fri Sep 09, 2011 6:57 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
I asked: Does the qmgr have operating channels of any kind currently? If not, it will likely not have a running listener.
What is the result from DISPLAY CHSTATUS(*) command?
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Sep 09, 2011 7:38 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
There's no indication that SYSTEM.DEFAULT.LISTENER.TCP has not been ALTERED to specify port 1414.
There's no indication that any attempt to determine what else is already listening on port 1414 has been made.
It would be nice to see more information from the MQ error logs, and something resembling a netstat output. |
|
| Back to top |
|
|
| gbaddeley |
| Posted: Fri Sep 09, 2011 9:45 am Post subject: |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
| exerk wrote: |
| Check etc/services, check inetd, and if that's where it's set remove the entries, then define and configure a Listener object. |
If there's nothing in /etc/services and /etc/inetd.conf, and runmqlsr is not running, you don't have a listener! That would be reasonable if there is no need for incoming channels from remote queue managers or clients.
_________________
Glenn |
|
| Back to top |
|
|
| exerk |
| Posted: Fri Sep 09, 2011 2:04 pm Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| gbaddeley wrote: |
| If there's nothing in /etc/services and /etc/inetd.conf, and runmqlsr is not running, you don't have a listener! That would be reasonable if there is no need for incoming channels from remote queue managers or clients. |
Yet the OP states he was able to connect on port 1420, so I'll go with the antiquated method theory... 
_________________
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 |
|
|
| gbaddeley |
| Posted: Sun Sep 11, 2011 5:35 pm Post subject: |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
| exerk wrote: |
| Yet the OP states he was able to connect on port 1420, so I'll go with the antiquated method theory... |
grep -i mq /etc/services /etc/inetd.conf should show all the MQ config lines for using inetd as the listener. OP, have you tried this?
_________________
Glenn |
|
| Back to top |
|
|
| mqmblife |
| Posted: Mon Sep 12, 2011 1:07 am Post subject: |
|
|
Novice
Joined: 24 Aug 2011
Posts: 21
|
| gbaddeley wrote: |
| exerk wrote: |
| Yet the OP states he was able to connect on port 1420, so I'll go with the antiquated method theory... |
grep -i mq /etc/services /etc/inetd.conf should show all the MQ config lines for using inetd as the listener. OP, have you tried this? |
Hi,
Thank You so much gbaddeley!!  Command grep -i mq /etc/services worked, it showed me all the MQ config lines. I thank each and every one who helped me in getting this solved.
Regards
Venkat |
|
| Back to top |
|
|
| Toronto_MQ |
| Posted: Mon Sep 12, 2011 9:31 am Post subject: |
|
|
Master
Joined: 10 Jul 2002
Posts: 263
Location: read my name
|
| mqmblife wrote: |
| gbaddeley wrote: |
| exerk wrote: |
| Yet the OP states he was able to connect on port 1420, so I'll go with the antiquated method theory... |
grep -i mq /etc/services /etc/inetd.conf should show all the MQ config lines for using inetd as the listener. OP, have you tried this? |
Hi,
Thank You so much gbaddeley!! Command grep -i mq /etc/services worked, it showed me all the MQ config lines. I thank each and every one who helped me in getting this solved.
Regards
Venkat |
Read a few posts above. You should get everything out of inetd and into a listener object, ASAP. |
|
| Back to top |
|
|
|
|
