| Author |
Message
|
| satya_jammy |
 Posted: Fri Oct 16, 2009 2:31 am Post subject: Unable to connect to the Remote QM's having '_ ' in its name |
 |
|
Acolyte
Joined: 01 Oct 2009
Posts: 66
|
HI
Did any one tried Connecting to th remote QM which is having _ as part of its name exampe RemoteQM_1422 . i know _ is a valid character as per naming conventions. i have two QM's which are running in remote machine
ex: RemoteQM_1422 and RemoteQM
i am able to connect o the QM (RemoteQM )from MQexplorer successfully. But i am unable to connect to the QM RemoteQM_1422. i have checked the listner, command server, SVRCONN channel everything is runniing fine for both the QM's. The only difference i can point out between these two QM's are the one which i am unable to connect is having _ in its name.
Any comments..?  |
|
| Back to top |
|
 |
| smdavies99 |
| Posted: Fri Oct 16, 2009 2:52 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
What error are you getting?
If the remote machine protected by a firewall? If so, is that the port the Listener running on open?
You do have a listener configured on a different port to the first QMGR don't you?
Is there anytihng in the logs of the qmgr that you can't connect to?
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| Rahul999 |
| Posted: Fri Oct 16, 2009 2:55 am Post subject: |
|
|
Centurion
Joined: 14 Mar 2007
Posts: 134
|
yes.. provide us the error please. And which version of MQ are you working .. i believe there was a limitation on the number of characters in queue manager name.(max 8 or 12) not sure 
_________________
"For all your days be prepared, and meet them ever alike.
When you are the anvil, bear - when you are the hammer, strike."
- Edwin Markham |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Fri Oct 16, 2009 3:01 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
| Rahul999 wrote: |
| yes.. provide us the error please. And which version of MQ are you working .. i believe there was a limitation on the number of characters in queue manager name.(max 8 or 12) not sure |
The length of Queue Manager Names is 48 Characters. You can check this in the docs or looking at cmqc.h if you are so inclined. Message Broker 6.* uses the following name for its default QM on distributed platforms.
WBRK61_DEFAULT_QUEUE_MANAGER
Which is plainly longer than 8 or 12 characters.
Of course, Z/OS might be different (strange beasts those Mainframes) 
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| exerk |
| Posted: Fri Oct 16, 2009 3:33 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| smdavies99 wrote: |
| ...Of course, Z/OS might be different (strange beasts those Mainframes) |
Four character sub-system name limitation (which now exhausts my z/OS knowledge). I'm not sure, but I think there is a seven character limit on HP-NSS.
EDIT: Having checked the Quick Beginnings for WMQ V5.3 on HP-NSS, I now see that yet again I am talking from a different orifice than normal 
_________________
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 |
|
|
| satya_jammy |
| Posted: Fri Oct 16, 2009 5:16 am Post subject: |
|
|
Acolyte
Joined: 01 Oct 2009
Posts: 66
|
No errros are generated in the log which are related to connectivity
My QM name is CONPROD_1422 listener is running for this QM and the port is also opened (port number is listed in /etc/services) .
ps -ef |grep -i runmqlsr
mqm 12917 1 0 Sep 11 ? 0:00 runmqlsr -m CONPROD_1422 -t tcp - p 1422
dspmqcsv CONPROD_1422
WebSphere MQ Command Server Status . . : Running
Here is my MQ version:
Name: WebSphere MQ
Version: 530.7 CSD07
CMVC level: p530-07-L040527
BuildType: IKAP - (Production) |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Fri Oct 16, 2009 5:25 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
How do you know that you cannot connect? What evidence do you see? Each MQ call returns a ReasonCode. What ReasonCode did your application return from the MQCONNect?
_________________
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 Oct 16, 2009 5:26 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| satya_jammy wrote: |
| Version: 530.7 CSD07 |
Yeesh - upgrade! To CSD 14 at least!
If no errors are generated in the log which are related to connectivity, what errors are generated?
There's certainly no problem with this qmgr name (as you correctly say, it's a valid character in the name) and if you were using a supported version of WMQ you could raise a PMR.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| satya_jammy |
| Posted: Fri Oct 16, 2009 5:45 am Post subject: |
|
|
Acolyte
Joined: 01 Oct 2009
Posts: 66
|
Hi,
it seems the issue is with the Port number.. it seems it is not opened.
when i am doing telnet using hostname(1422) it is not working. at the same time when using hostname(1420) it is working.
in the /etc/services i found an entry
MQS04 1422/tcp # MQseries
is that doesnt mean this port is opened? Now how i can make this port working?? |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Oct 16, 2009 6:27 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| satya_jammy wrote: |
| is that doesnt mean this port is opened? Now how i can make this port working?? |
No, that just means the port's assigned. To open it, speak to your network people.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| satya_jammy |
| Posted: Fri Oct 16, 2009 7:12 am Post subject: |
|
|
Acolyte
Joined: 01 Oct 2009
Posts: 66
|
In /etc/services. For MQ series i found two different type of entries .
MQSeries 1414/tcp # MQSeries listener
MQS01 1415/tcp # MQseries
what is the difference b/w naming it MQseries and MQS01. what is MQs01.
if i create a new Qmanager which i want to run it with a new port 4444 what entry i need to make so that apps connect to that QM. |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Oct 16, 2009 7:18 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| satya_jammy wrote: |
| if i create a new Qmanager which i want to run it with a new port 4444 what entry i need to make so that apps connect to that QM. |
Don't play with /etc/services in v5.3.7 - use runmqlsr.
You'll find all the details in the documentation.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Fri Oct 16, 2009 7:23 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| Quote: |
| what is the difference b/w naming it MQseries and MQS01. what is MQs01. |
WMQ object names are case-sensitive. MQS01 is different from MQs01. An application trying to connect to MQS01 will fail if it uses a qmgr name that is not exactly identical to the name of the qmgr. Close doesn't count.
| Quote: |
| if i create a new Qmanager which i want to run it with a new port 4444 what entry i need to make so that apps connect to that QM. |
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.
_________________
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 Oct 16, 2009 7:33 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| 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.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Fri Oct 16, 2009 7:37 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
Yep, but runmqlsr is in v5.
_________________
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 |
|
|
|
|
