| Author |
Message
|
| Pats21 |
 Posted: Thu Sep 18, 2008 3:33 am Post subject: [SOLVED] UPES posting messages to QM other then FMCQM |
 |
|
Disciple
Joined: 08 Sep 2006
Posts: 154
|
Hi,
Just wanted clarification and how do we implement the following.
I think we can use UPES to put messages to a QM which is not the one used by MQWF administration (namely FMCQM).
Can anyone let me know how is this achievable?
I have a UPES which is configured on a MQ queue which is on a QM other than FMCQM.
The only setting I can see is that the UPES has the mentioning of the queue name and the QM name.
Is there any other setting that needs to be done ?
The main reason I am asking this question is that I am getting an error MQRC 2087, i.e. UNKNOWN_REMOTE_Q_MGR, when my program activity is trying to put messages into the queue which is defined in other QM.
Regards,
Pats ...
Last edited by Pats21 on Thu Oct 02, 2008 10:43 pm; edited 1 time in total |
|
| Back to top |
|
 |
| Pats21 |
| Posted: Thu Sep 25, 2008 3:41 am Post subject: |
|
|
Disciple
Joined: 08 Sep 2006
Posts: 154
|
Hi All,
I am still struggling to find an answer to the below  .
Hope I was able to convey the issue that I am facing correctly.
Let me know if anyone needs any more details.
Right now I do not have any clues on where to start from.
Pats ... |
|
| Back to top |
|
|
| mqjeff |
| Posted: Thu Sep 25, 2008 3:44 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Any application that can write to MQ can send a message to another queue manager.
Even without creating a client connection to a remote queue manager. |
|
| Back to top |
|
|
| Ratan |
| Posted: Thu Sep 25, 2008 7:57 am Post subject: |
|
|
Grand Master
Joined: 18 Jul 2002
Posts: 1245
|
If your Upes QM is a not same as your WF QM then you will need to set up intercommunication between your WF QM and the UPES QM. The name of the XmitQ on WF QM should be the name of the UPES QM.
_________________
-Ratan |
|
| Back to top |
|
|
| Pats21 |
| Posted: Fri Sep 26, 2008 12:14 am Post subject: |
|
|
Disciple
Joined: 08 Sep 2006
Posts: 154
|
HI,
Thanks for your inputs.
Initially I also thought the same, that there has to be an intercomm. between the two QM's.
But I have another setup which is working fine, without any errors.
In this setup there is no intercomm. between the WF QM and the QM used by UPES.
Hence I am not sure what needs to be done now.
Also let me know is there any other way to set the intercomm. between QM's, other than setting the TX queue and channels.
Pats ... |
|
| Back to top |
|
|
| jmac |
| Posted: Fri Sep 26, 2008 8:20 am Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
Pats:
I agree with Ratan, this has to be an MQ configuration issue. The only thing I can suggest since you have one working environment, is a strict comparison of the two environments to see where the difference lies. I strongly suspect you will find some small MQ glitch.
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
| Pats21 |
| Posted: Thu Oct 02, 2008 10:34 pm Post subject: |
|
|
Disciple
Joined: 08 Sep 2006
Posts: 154
|
Hi all ...
Thanks a lot for your support, I was able to solve the issue ... 
As you guys had said, it was nothing to do with MQWF configuration. The issue was purely with MQ Configuration.
It was a MQ concept, which I had ignored.
In a MQ cluster one can put a message onto a queue which is not shared in the cluster and which is not the QM to which you have connected to, but is a part of the cluster, if you mention the remote queue manager property to the other QM while putting the message.
The same concept was applied here. I had to sort out the cluster and then things worked.
Regards,
Pats ... |
|
| Back to top |
|
|
|
|
