| Author |
Message
|
| harshatej1 |
 Posted: Fri Jan 31, 2014 11:40 am Post subject: port number |
 |
|
Acolyte
Joined: 20 Nov 2013
Posts: 61
|
Hi,
can you please tell me the command to know which port is being used by the queue manager?
MQ version: 5.1 |
|
| Back to top |
|
 |
| bruce2359 |
| Posted: Fri Jan 31, 2014 12:19 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
netstat
_________________
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 |
|
|
| Vitor |
| Posted: Fri Jan 31, 2014 12:25 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
If it's the same out of date MQv5.1 you were trying to install here, it's the port number you selected during the installation process....
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mqsiuser |
| Posted: Fri Jan 31, 2014 2:05 pm Post subject: |
|
|
Yatiri
Joined: 15 Apr 2008
Posts: 637
Location: Germany
|
1.
2.
| Code: |
runmqsc <QMGR_NAME>
display listener(*)
display listener(<LISTENER>) |
3. Default is 1414. If not 1414 then "try" 1415, 1416, ...
| Code: |
telnet <IP_or_hostname> 1414
telnet <IP_or_hostname> 1415
telnet <IP_or_hostname> 1416
... |
If telnet connects (no c:\> or linux/unix prompt any more), then the port is busy and it is *likely* a/your queue manager 
_________________
Just use REFERENCEs |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Fri Jan 31, 2014 4:34 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| mqsiuser wrote: |
2.
| Code: |
runmqsc <QMGR_NAME>
display listener(*)
display listener(<LISTENER>) |
|
DISPLAY LISTENER command not supported at OPs version of MQ.
_________________
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 |
|
|
| zpat |
| Posted: Fri Jan 31, 2014 11:55 pm Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
ps -ef | grep lsr
_________________
Well, I don't think there is any question about it. It can only be attributable to human error. This sort of thing has cropped up before, and it has always been due to human error. |
|
| Back to top |
|
|
| exerk |
| Posted: Sat Feb 01, 2014 2:17 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
You might also want to check for any MQSeries-related entries in /etc/inetd.conf
_________________
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 Feb 02, 2014 2:36 pm Post subject: |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
| exerk wrote: |
| You might also want to check for any MQSeries-related entries in /etc/inetd.conf |
and /etc/services. The MQ listener will be a separately started runmqlsr or use inetd. MQ LISTENER objects didn't exist 15 years ago.
_________________
Glenn |
|
| Back to top |
|
|
| exerk |
| Posted: Sun Feb 02, 2014 3:28 pm Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| gbaddeley wrote: |
| exerk wrote: |
| You might also want to check for any MQSeries-related entries in /etc/inetd.conf |
and /etc/services. The MQ listener will be a separately started runmqlsr or use inetd. MQ LISTENER objects didn't exist 15 years ago. |
True, but did not most people start it under control of inetd to ensure port ring-fencing? It was a long time ago, in an installation far away...
_________________
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 |
|
|
|
|
