| Author |
Message
|
| fjb_saper |
 Posted: Tue May 26, 2009 1:48 pm Post subject: |
 |
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Don't forget the all famed 2035...
_________________
MQ & Broker admin |
|
| Back to top |
|
 |
| Vitor |
| Posted: Tue May 26, 2009 2:27 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| fjb_saper wrote: |
| Don't forget the all famed 2035... |
Would have been my next guess; I plumped for 2059 as the less experienced tend to run without security.
But hey, wouldn't bet against you. 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| omerakhter |
| Posted: Tue May 26, 2009 10:25 pm Post subject: |
|
|
Novice
Joined: 19 May 2009
Posts: 22
|
Well doesn't work mean when I create a domain connection in toolkit; it says in a long message that Queue Manager is not running. I would reproduce the error and then copy the exact message.
When I followed the M-Q example which says that I have to install M-Q client on client machine and create a remote queue manager that connects to server's Queue Manager... and have to create a server connection channel on server. The problem in that example is that the server channel never goes up. The M-Q Explorer says "request accepted"; no error, nothing |
|
| Back to top |
|
|
| MQEnthu |
| Posted: Tue May 26, 2009 10:38 pm Post subject: |
|
|
Partisan
Joined: 06 Oct 2008
Posts: 329
Location: India
|
| omerakhter wrote: |
| Well doesn't work mean when I create a domain connection in toolkit; it says in a long message that Queue Manager is not running. I would reproduce the error and then copy the exact message. |
Provide the error details..
| omerakhter wrote: |
| client on client machine and create a remote queue manager that connects to server's Queue Manager... and have to create a server connection channel on server. The problem in that example is that the server channel never goes up. The M-Q Explorer says "request accepted"; no error, nothing |
Have you installed the WMQ client on client machine? Have you configured the client connection? If yes, how?
_________________
-----------------------------------------------
It is good to remember the past,
but don't let past capture your future |
|
| Back to top |
|
|
| omerakhter |
| Posted: Wed May 27, 2009 5:08 am Post subject: |
|
|
Novice
Joined: 19 May 2009
Posts: 22
|
This is the error message
This happens when I give the Queue Manager Name, ip address and port of server WMQ.
In the other example, I have WMQ 6 on my machine while on server it WMQ 7. I havent installed any client as I thought it would be there in WMQ 6 installation... |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed May 27, 2009 5:11 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| omerakhter wrote: |
| I havent installed any client as I thought it would be there in WMQ 6 installation... |
What led you to this erronious conclusion?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed May 27, 2009 5:16 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| Quote: |
| MQ Reason Code 2059 while trying to connect |
We have a winner! |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed May 27, 2009 5:22 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| mqjeff wrote: |
| Quote: |
| MQ Reason Code 2059 while trying to connect |
We have a winner! |
Thank you, thank you. I'd like to thank <insert dull acceptance speech here>
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| omerakhter |
| Posted: Thu May 28, 2009 1:01 am Post subject: |
|
|
Novice
Joined: 19 May 2009
Posts: 22
|
| Vitor wrote: |
| omerakhter wrote: |
| I havent installed any client as I thought it would be there in WMQ 6 installation... |
What led you to this erronious conclusion? |
Because in most softwares, client is installed when you install "full" software
Anyway, what I need to do now? Install a client of WMQ and then try again? I dont really understand why a client is required if there is a "TCP listener" on some port on server, the connection should be established! |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu May 28, 2009 1:10 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| omerakhter wrote: |
| Because in most softwares, client is installed when you install "full" software |
In WMQ, the client and the server are 2 separate products. There are good & sufficient reasons why you wouldn't want a client installed on the server machine.
| omerakhter wrote: |
| Anyway, what I need to do now? |
Spend more time with the documentation. Your comment:
| omerakhter wrote: |
| I dont really understand why a client is required if there is a "TCP listener" on some port on server, the connection should be established! |
shows a fundamental lack of understanding about how all this fits together. Without this knowledge, you're in for a long and needlessly painful journey.
To get you started, the answer to your question is that the "TCP listener" is what the client is connecting to not an end in itself. Without a client install, you've nothing to connect to this TCP listener and hence it doesn't work for you. The listener also does more than allow client connections so exists even in the absense of clients (to pre-empt your next question).
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| omerakhter |
| Posted: Thu May 28, 2009 1:19 am Post subject: |
|
|
Novice
Joined: 19 May 2009
Posts: 22
|
| Quote: |
| "TCP listener" is what the client is connecting to not an end in itself. Without a client install, you've nothing to connect to this TCP listener and hence it doesn't work for you. |
You mean WMQ client? I could not understand what you mean by "not an end in itself"
Well for TCP connection, I listener recieves a connection on a port, which we can specify in toolkit as well as the host name of the server. Intuitively, it should have worked.
Anyway, they have designed it to work another way. Let me install WMQ client and come back. |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu May 28, 2009 1:29 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| omerakhter wrote: |
| You mean WMQ client? I could not understand what you mean by "not an end in itself" |
I mean it's not an end in itself in the way an TCP listener is for a web server. In that scenario it just sits and listens, and traffic arrives on the port. The listener is a piece of IBM software that expects to be connected to another piece of IBM software.
| omerakhter wrote: |
| Well for TCP connection, I listener recieves a connection on a port, which we can specify in toolkit as well as the host name of the server. Intuitively, it should have worked. |
- it's not a TCP connection, it's a client channel
- what you're specifying is the host and port on which the matching software is waiting
- Intuition is a poor guide compared to the product documentation
| omerakhter wrote: |
| Anyway, they have designed it to work another way. |
And it's this design which is why we've all paid the license fee to IBM rather than written socket code for free.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
