|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
z/os shared queues question |
« View previous topic :: View next topic » |
Author |
Message
|
smeunier |
Posted: Mon Nov 03, 2014 9:03 am Post subject: z/os shared queues question |
|
|
 Partisan
Joined: 19 Aug 2002 Posts: 305 Location: Green Mountains of Vermont
|
A Parallel Sysplex is being created where two LPARS will be part of the sysplex. Each LPAR has its own MQ Manager installed. Both QMGR's will be part if the same Queue Sharing Group. A shared queue will be created for each of the QMGR's to write to(PUT only), creating a common repository of messages between the two LPAR's. Both of these QMGRS are currently in a cluster along with other QMGR's on AIX.
Shared queues can only be defined local to the z/os environment, but the data in this shared queue needs to be available to QMGRS outside of Z/os on one of the AIX QMGR's.
My question is: How do share these message, so that the AIX QMGR is the recipient of the messages (as would be possible with Remote Q or as a Clustered Q)?
Seems like shared queues are great for sharing within the QSG, but not outside of it. How would I resolve moving the data off the shared queue to a remote (non-Z/os) QMGR, using MQ? |
|
Back to top |
|
 |
Vitor |
Posted: Mon Nov 03, 2014 9:11 am Post subject: Re: z/os shared queues question |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
smeunier wrote: |
My question is: How do share these message, so that the AIX QMGR is the recipient of the messages (as would be possible with Remote Q or as a Clustered Q)? |
Something would need to send it to a remote queue or a clustered queue.
smeunier wrote: |
Seems like shared queues are great for sharing within the QSG, but not outside of it. |
A QSG is an exclusively z/OS construct; it uses a specific piece of the z/OS archtecture to make this work.
smeunier wrote: |
How would I resolve moving the data off the shared queue to a remote (non-Z/os) QMGR, using MQ? |
An application on one, the other or both of the LPARs would need to send it. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
PeterPotkay |
Posted: Mon Nov 03, 2014 1:38 pm Post subject: Re: z/os shared queues question |
|
|
 Poobah
Joined: 15 May 2001 Posts: 7722
|
smeunier wrote: |
creating a common repository of messages between the two LPAR's. |
A repository? Are you using this queue like a database? _________________ Peter Potkay
Keep Calm and MQ On |
|
Back to top |
|
 |
mqjeff |
Posted: Mon Nov 03, 2014 2:00 pm Post subject: Re: z/os shared queues question |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
PeterPotkay wrote: |
smeunier wrote: |
creating a common repository of messages between the two LPAR's. |
A repository? Are you using this queue like a database? |
If this is generally the area you are thinking of - that several queues across the MQ network should all receive copies of the same message... then you should use Pub/Sub, not try and use shared queues.
But you shouldn't expect that you can query the contents of a queue in the same way you can query the contents of a database table. |
|
Back to top |
|
 |
smeunier |
Posted: Tue Nov 04, 2014 9:04 am Post subject: |
|
|
 Partisan
Joined: 19 Aug 2002 Posts: 305 Location: Green Mountains of Vermont
|
Perhaps the term "common repository" was mis-leading
Its more like a focal point for delivery of messages to maintain synchronicity of message delivery between LPARS. Message Sequence is very important.
As suspected and confirmed by Vitor, a "mover" application would be needed to do the actual distribution to remote QMGR outside of the QSG. So, NO, the shared queue is not being used like a DB, but just a transition point.
I agree, that this lends itself to a Pub/Sub paradigm, but as so often happens, the design can get corrupted at the hands of legacy application owners who can't see the light ( or just to damn lazy to migrate from point/point to Pub/Sub).
In either case, my question was answered.
My apologies for this getting posted in the MQ Security forum. A tirgger finger mistake  |
|
Back to top |
|
 |
mqjeff |
Posted: Tue Nov 04, 2014 9:10 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
smeunier wrote: |
Perhaps the term "common repository" was mis-leading
Its more like a focal point for delivery of messages to maintain synchronicity of message delivery between LPARS. Message Sequence is very important |
I'm not sure that a shared queue solves that. With a shared queue, LPAR 1 could process message 1,4,5,8,11,etc, whilst concurrently LPAR 2 would be processing message 2,3,6,7,9,10.... So message 2 could very easily be processed completely before message 1, and etc. etc. etc. |
|
Back to top |
|
 |
|
|
 |
|
Page 1 of 1 |
|
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
|
|
|
|