|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
MQSWF High Availability and MQ Queue-Sharing Groups on z/OS |
« View previous topic :: View next topic » |
Author |
Message
|
robsdman |
Posted: Thu Mar 06, 2003 2:51 pm Post subject: MQSWF High Availability and MQ Queue-Sharing Groups on z/OS |
|
|
 Apprentice
Joined: 23 Aug 2002 Posts: 27
|
Has anyone configured MQWorkflow z/OS or 390 to use MQSeries Queue-Sharing Groups?
This basically provides an extremely High Available solution for MQSeries applications running on z/OS or 390. Queues would reside in a coupling facility providing a single location where cloned systems can pull messages from. Peer recovery also allows the detection of uncommitted messages between qmgrs in the group. When a qmgr fails those messages go back into the coupling facility and a working system would pull them.
This is an excerpt from the MQ5.3 z/OS Concepts and Planning Guide,
I'm wondering if anyone sees an issue that might apply to MQWorkflow.
Applications that are not suitable for use with shared queues
Some features of WebSphere MQ are not supported when you are using shared queues, so applications that use these features are not suitable for the shared queue environment. You should consider the following points when designing your shared queue applications:
1) Messages on shared queues cannot be greater than 63 KB in size. Because Coupling Facility storage is limited, you must also consider the number of messages to be generated by the application to ensure that the messages will not fill the queue. However, remember that you can monitor the queue and start more versions of the application on different queue managers to service it if this is a problem.
2) Queue indexing is limited for shared queues. If you want to use the message identifier or correlation identifier to select the message you want to get from the queue, the queue must have the correct index defined. If you do not define a queue index, applications can only get the next available message.
3) You cannot use temporary dynamic queues as shared queues. You can use permanent dynamic queues however. The models for shared dynamic queues have a DEFTYPE of SHAREDYN (shared dynamic) although they are created and destroyed in the same way as PERMDYN (permanent dynamic) queues. |
|
Back to top |
|
 |
jmac |
Posted: Thu Mar 06, 2003 3:57 pm Post subject: Re: MQSWF High Availability and MQ Queue-Sharing Groups on z |
|
|
 Jedi Knight
Joined: 27 Jun 2001 Posts: 3081 Location: EmeriCon, LLC
|
robsdman wrote: |
1) Messages on shared queues cannot be greater than 63 KB in size. Because Coupling Facility storage is limited, you must also consider the number of messages to be generated by the application to ensure that the messages will not fill the queue. However, remember that you can monitor the queue and start more versions of the application on different queue managers to service it if this is a problem. |
robsdman:
MQWF can write messages up to 100M by default, so this may be a problem. _________________ John McDonald
RETIRED |
|
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
|
|
|
|