|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
2059.. what am I doing wrong?? |
« View previous topic :: View next topic » |
Author |
Message
|
bruce2359 |
Posted: Wed Mar 18, 2009 11:40 am Post subject: |
|
|
 Poobah
Joined: 05 Jan 2008 Posts: 9482 Location: US: west coast, almost. Otherwise, enroute.
|
Prove to us that you set both environment variables.
Prove to us that the client channel table name is in the path specified in the environment variables.
Prove to us that the client channel table is in the path specified in the environment variable.
Do this by posting the complete interaction. Or using the export command (UNIX) or SET command (Windows) on the client platform.
If I say 'please' will you comply with my request? If so, please do these things. _________________ 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: Wed Mar 18, 2009 11:40 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
zpat wrote: |
Test connection with a known program like RFHUTILC (support pac IH03). |
amqscnxc *is* a known program, zpat. |
|
Back to top |
|
 |
JosephGramig |
Posted: Wed Mar 18, 2009 12:42 pm Post subject: |
|
|
 Grand Master
Joined: 09 Feb 2006 Posts: 1244 Location: Gold Coast of Florida, USA
|
First, prove MQ is listening:
From the client:
telnet masked.xyx.com 1414
You should get a rather blank screen. To get out, give it ctrl+]
If you got an error, your going against the wrong machine name and or port number.
Next, make sure that MQSERVER is not set. It over rides MQCHLLIB and MQCHLTAB. |
|
Back to top |
|
 |
bruce2359 |
Posted: Wed Mar 18, 2009 12:51 pm Post subject: |
|
|
 Poobah
Joined: 05 Jan 2008 Posts: 9482 Location: US: west coast, almost. Otherwise, enroute.
|
Quote: |
Next, make sure that MQSERVER is not set. |
I've asked for this twice. I'm not optimistic. _________________ 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 |
|
 |
girish_tharwani |
Posted: Wed Mar 18, 2009 12:58 pm Post subject: |
|
|
 Voyager
Joined: 01 Aug 2001 Posts: 88 Location: Pune, India
|
As far as I can see from the comments provided with "known" program amqscnxc which comes budled with WMQ, it does not need MQSERVER or client connection channel so why are the env variables an issue? I am puzzled. |
|
Back to top |
|
 |
bruce2359 |
Posted: Wed Mar 18, 2009 1:06 pm Post subject: |
|
|
 Poobah
Joined: 05 Jan 2008 Posts: 9482 Location: US: west coast, almost. Otherwise, enroute.
|
Quote: |
need to set MCAUSR on channel even though my local id on Windows is part of mqm group on HP-UX? |
Reference to CLNTCONN and SVRCONN, and Win and HPUX in this post lead me to believe this was an WMQ Client app.
I'll ask: is this a qmgr-to-qmgr (with SDR and RCVR channels) or client-to-qmgr (with CLNTCONN and SVRCONN channels)? _________________ 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 |
|
 |
girish_tharwani |
Posted: Wed Mar 18, 2009 1:23 pm Post subject: |
|
|
 Voyager
Joined: 01 Aug 2001 Posts: 88 Location: Pune, India
|
Its client-to-qmgr (with CLNTCONN and SVRCONN channels) but the program I am using does not rely on MQSERVER or client channel table. The information supplied at invocation of this program is used to establish the client connection
amqscnxc -x conname -c channelname Qmgr
It does not matter if I am running it on my windows desktop or on the HP-UX box which has my queue manager, it will create client connection only.
Its running successfully when I run it on HP-UX but it fails on my windows desktop. |
|
Back to top |
|
 |
bruce2359 |
Posted: Wed Mar 18, 2009 1:48 pm Post subject: |
|
|
 Poobah
Joined: 05 Jan 2008 Posts: 9482 Location: US: west coast, almost. Otherwise, enroute.
|
Quote: |
Its running successfully when I run it on HP-UX but it fails on my windows desktop. ... but if i log on to the server with that id and run the same program with same parameters, it works..
$ amqscnxc -x "*****(1414)" -c IBCONN
Sample AMQSCNXC start
Connecting to the default queue manager
using the server connection channel IBCONN
on connection name mwdev1.bd.com(1414).
Connection established to queue manager DCLNTCONN1 |
Yes, it works when you run the app on the same platform as the queue manager - because the application connected to the default quque manager.
It did not connect to the qmgr you specified because that qmgr was not found (mqrc 2059). Rather, it connected to the default qmgr, of which there can only be one in an instance of an o/s. _________________ 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 |
|
 |
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|
|
|