| Author |
Message
|
| mqonnet |
 Posted: Tue Jun 04, 2002 8:23 am Post subject: MQexplorer on Win2K... |
 |
|
Grand Master
Joined: 18 Feb 2002
Posts: 1114
Location: Boston, Ma, Usa.
|
I am facing a peculiar problem.
I am able to connect to a Queue manager using MQExplorer, which is connecting to the qm at the remote end as a Client from Win2K. But when i run a sample app, which i built using the client libraries does not work. This sample app is the standard amqsput program.
Now since i am able to connect to the QM at remote end using MQExplorer, the setup is correct. Listener running at the right port, QM running, Case sensitivity of QM name, MQSERVER variable having the right value, principal defined properly on the remote end.
But even after all this is I get 2058/2059 intermittently. I have done this 100's of times, but this one i am able to hit/reproduce repeatedly.
Was just wondering if MQExplorer does something undercovers that anyone has come accross, which might throw some light to this issue.
Cheers.
Kumar
_________________
IBM Certified WebSphere MQ V5.3 Developer
IBM Certified WebSphere MQ V5.3 Solution Designer
IBM Certified WebSphere MQ V5.3 System Administrator |
|
| Back to top |
|
 |
| mrlinux |
| Posted: Tue Jun 04, 2002 9:44 am Post subject: |
|
|
Grand Master
Joined: 14 Feb 2002
Posts: 1261
Location: Detroit,MI USA
|
Try setting MQSERVER=SYSTEM.ADMIN.SVRCONN/TCP/HOST(PORT)
That is the server conn channel that MQExpolrer uses.
_________________
Jeff
IBM Certified Developer MQSeries
IBM Certified Specialist MQSeries
IBM Certified Solutions Expert MQSeries |
|
| Back to top |
|
|
| mqonnet |
| Posted: Tue Jun 04, 2002 10:04 am Post subject: |
|
|
Grand Master
Joined: 18 Feb 2002
Posts: 1114
Location: Boston, Ma, Usa.
|
Jeff,
Mqserver variable was set as you mentioned. And thats the reason i was able to connect to the QM using mq explorer. But what makes me scratch my head is, why i was unable to connect using a sample client prog when i was able to connect using the same config to the QM via MQExplorer.
Cheers.
Kumar
_________________
IBM Certified WebSphere MQ V5.3 Developer
IBM Certified WebSphere MQ V5.3 Solution Designer
IBM Certified WebSphere MQ V5.3 System Administrator |
|
| Back to top |
|
|
| mrlinux |
| Posted: Tue Jun 04, 2002 10:11 am Post subject: |
|
|
Grand Master
Joined: 14 Feb 2002
Posts: 1261
Location: Detroit,MI USA
|
Well the 2059 could mean network issues. The 2058 indicates you connected to a MQSeries Listener and the queue manager name you passed didnt match the queue manager name for that listener.
_________________
Jeff
IBM Certified Developer MQSeries
IBM Certified Specialist MQSeries
IBM Certified Solutions Expert MQSeries |
|
| Back to top |
|
|
| mqonnet |
| Posted: Tue Jun 04, 2002 10:32 am Post subject: |
|
|
Grand Master
Joined: 18 Feb 2002
Posts: 1114
Location: Boston, Ma, Usa.
|
Jeff.
Well the return codes are fine. But you have to bear in mind that in some cases return codes do not convey the exact problem.
What i noticed is, if i have my Listener running i get 2058. And if i dont have it running, i get 2059. In the latter case, it suggests that the client was unable to connect because it was not able to locate the QM(because the listener was not running and it could not establish the communication with qm). But in the former. Since my listener was running and i had only one listener at this moment in the entire system, i would assume that it went and processed my request. Instead it gave me 2058.
As for errors like QM name. It was the first thing i did.
Cheers.
Kumar
_________________
IBM Certified WebSphere MQ V5.3 Developer
IBM Certified WebSphere MQ V5.3 Solution Designer
IBM Certified WebSphere MQ V5.3 System Administrator |
|
| Back to top |
|
|
| kolban |
| Posted: Tue Jun 04, 2002 11:07 am Post subject: |
|
|
Grand Master
Joined: 22 May 2001
Posts: 1072
Location: Fort Worth, TX, USA
|
| There is no relationship between MQExplorer and the MQSERVER environment variable. |
|
| Back to top |
|
|
| jlamond |
| Posted: Mon Jun 10, 2002 3:12 am Post subject: |
|
|
Voyager
Joined: 28 May 2002
Posts: 94
Location: Paris
|
Have you try of using amqsputc instead of amqsput... amqsputc is for a cleint connection to a remote Queue Manager where amqsput is for a local Queue Manager connection. Then of course you will need a client channel connection.
Regards,
JM
_________________
Jean-Marc |
|
| Back to top |
|
|
|
|
