Author |
Message
|
George Carey |
Posted: Mon Apr 30, 2012 10:48 am Post subject: What port is MQ client connected application connecting on? |
|
|
Knight
Joined: 29 Jan 2007 Posts: 500 Location: DC
|
Where is the MQ command that will give me what port an MQ client connected application is connecting to an MQ Server on??
If I didn't start the channels myself or have access to MQSERVER environment variable or CCDT table how could one determine a posteriori(after the fact) what port a MQ client channel is using to connect to the MQ Server?
Not, MQExplorer or MQMON, channel status, qmgr application connection list, dis chl, nothing would give me a port number association to an MQ client channel.
Case in point I have created two listeners on an MQ server and two MQ client svrconn channels to connect two different utilities to the MQ Server ... one the MQExplorer(MS0T) on port 1234 and the other MQMON(MO71) ... on port 1235 say. After utility start up I was not sure which port was actually being used and was trying to find a command that had a mapping to the port. My search was in vain.
One could ham handedly stop a listener and see which channel went inactive and one can stop all connections from an IP but both utilities were started from the same IP and this is just as ham handed. Is there no such MQ command? Shouldn't there be? Just one more column for some command output with heading 'Connection Port'.
GTC
P.S. got nothing on MQ List Server on this, so trying here. _________________ "Truth is ... grasping the virtually unconditioned",
Bernard F. Lonergan S.J.
(from book titled "Insight" subtitled "A Study of Human Understanding") |
|
Back to top |
|
 |
mqjeff |
Posted: Mon Apr 30, 2012 11:42 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
will show you the PID of the amq* process that has accepted the socket. you should, particularly on unix, then be able to tie that back to one of the two listeners. |
|
Back to top |
|
 |
George Carey |
Posted: Mon Apr 30, 2012 11:49 am Post subject: pid check |
|
|
Knight
Joined: 29 Jan 2007 Posts: 500 Location: DC
|
Will check it out ... sounds reasonable. _________________ "Truth is ... grasping the virtually unconditioned",
Bernard F. Lonergan S.J.
(from book titled "Insight" subtitled "A Study of Human Understanding") |
|
Back to top |
|
 |
George Carey |
Posted: Mon Apr 30, 2012 12:58 pm Post subject: nope but ... |
|
|
Knight
Joined: 29 Jan 2007 Posts: 500 Location: DC
|
The process id from the dis conn(*) all command for both channels give the same pid and it is for the amqrmppa process.
The pid from the dis conn(*) all command does not give the runmqlsr process id, unfortunately.
However in relooking at this I happened to do the simple dis chs(*) all command again ... I don't know how I missed it but there it was at the end of the LOCLADDR IPv6 formatted IP address was sitting plain as day the Port number that the SVRCONN channel was using!!
e.g. LOCLADDR(::ffff:1.2.3.4(1234))
So thanks for the redirection ... anyway. _________________ "Truth is ... grasping the virtually unconditioned",
Bernard F. Lonergan S.J.
(from book titled "Insight" subtitled "A Study of Human Understanding") |
|
Back to top |
|
 |
mqjeff |
Posted: Mon Apr 30, 2012 1:07 pm Post subject: Re: nope but ... |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
George Carey wrote: |
The process id from the dis conn(*) all command for both channels give the same pid and it is for the amqrmppa process. |
Yeah, that's the process spun up by the listener that holds the thread.
You should be able to use the parent pid to determine which listener started this amqrmppa process, and thus which runmqlsr process started it...
George Carey wrote: |
However in relooking at this I happened to do the simple dis chs(*) all command again ... I don't know how I missed it but there it was at the end of the LOCLADDR IPv6 formatted IP address was sitting plain as day the Port number that the SVRCONN channel was using!!
e.g. LOCLADDR(::ffff:1.2.3.4(1234))
So thanks for the redirection ... anyway. |
I really did think it was there, but rather than double-checking it when I actually had an active client connection (rather than no active client connections...), I assumed you'd double-checked it already. |
|
Back to top |
|
 |
George Carey |
Posted: Mon Apr 30, 2012 1:16 pm Post subject: double checked |
|
|
Knight
Joined: 29 Jan 2007 Posts: 500 Location: DC
|
I thought I doubled checked as well (actually I know I did) l ... maybe not when the channel was active or maybe not when I did an 'all' option ... don't know???
And on that parent process Id ... nope ... ppid 1 _________________ "Truth is ... grasping the virtually unconditioned",
Bernard F. Lonergan S.J.
(from book titled "Insight" subtitled "A Study of Human Understanding") |
|
Back to top |
|
 |
mqjeff |
Posted: Mon Apr 30, 2012 1:21 pm Post subject: Re: double checked |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
George Carey wrote: |
And on that parent process Id ... nope ... ppid 1 |
 |
|
Back to top |
|
 |
|