| Author |
Message
|
| Al Pacino |
 Posted: Mon May 09, 2011 12:00 am Post subject: distribution list |
 |
|
Centurion
Joined: 19 Aug 2005
Posts: 114
|
Hello folks,
I was wondering if distribution list can be used in an MQ clustered environment. Basically a message need to be put a cross the same queue on different queue managers within the cluster at the same time. If yes , this is something to be done on the application side and not the MQ ?
Thanks
_________________
"We can't solve problems by using the same kind of thinking we used
when we created them." |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Mon May 09, 2011 1:25 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Distribution lists are always done at the application side.
and there's nothing that prevents them from being used with clustered destinations.
A distribution list is an application level structure that provides a set of qm/qnames to MQPUT instead of a single qm/qname. And the application receives back a set of MQRC/MQCC for each of the destinations chosen. |
|
| Back to top |
|
|
| Al Pacino |
| Posted: Mon May 09, 2011 1:40 am Post subject: |
|
|
Centurion
Joined: 19 Aug 2005
Posts: 114
|
Hi Mqjeff,
So I was reading that , this can't be supported on zOS which is the environment we are using at the moment. 
Beside using pub/sub, any other alternative ways to set up a distributed list alike solution on MQ cluster environment running on zOS?
Thanks
_________________
"We can't solve problems by using the same kind of thinking we used
when we created them." |
|
| Back to top |
|
|
| mvic |
| Posted: Mon May 09, 2011 1:43 am Post subject: Re: distribution list |
|
|
Jedi
Joined: 09 Mar 2004
Posts: 2080
|
You want one-to-many without using pub/sub?
May I ask why? |
|
| Back to top |
|
|
| mqjeff |
| Posted: Mon May 09, 2011 1:44 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Write a loop that issues multiple MQPUTs.
There isn't a significant amount of advantage of using a destination list on MQ versus issuing multiple PUTS as far as I know. It's a convenience method rather than anything else.
I suppose there is in theory some difference in transactional behavior, but again I don't think it's large?
As well, with a distribution list, you lose the ability to react if one destination fails. MQ will always complete all of the PUTS and then tell you which ones did or didn't fail. With a loop, you can change your mind. |
|
| Back to top |
|
|
| Al Pacino |
| Posted: Mon May 09, 2011 2:50 am Post subject: |
|
|
Centurion
Joined: 19 Aug 2005
Posts: 114
|
Thanks much guys..
@mvic , nothing against the pub/sub solution ,, I am actually pushing that route ,, it just the client against introducing pub/sub at this point since this is happening with only one queue where they have to distribute the data.
_________________
"We can't solve problems by using the same kind of thinking we used
when we created them." |
|
| Back to top |
|
|
|
|
