| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| z/OS qsg shared queue in a cluster setup |
« View previous topic :: View next topic » |
| Author |
Message
|
| migz0901 |
 Posted: Tue Sep 13, 2022 2:01 am Post subject: z/OS qsg shared queue in a cluster setup |
 |
|
Apprentice
Joined: 01 Nov 2012
Posts: 28
|
Hi Peeps,
I have a shared queues (qsg) in a cluster setup MQ1lpar1) and MQ2(lpar2) qmgrs.
Is DEFBIND(OPEN) parameter in my qlocal has impact for incoming messages when one lpar is down due to IPL?
Thanks in advance to those who will reply.
Cheers,
Migz |
|
| Back to top |
|
 |
| bruce2359 |
| Posted: Tue Sep 13, 2022 5:12 am Post subject: Re: shared queue in a cluster setup |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| migz0901 wrote: |
Hi Peeps,
I have a shared queues (qsg) in a cluster setup MQ1lpar1) and MQ2(lpar2) qmgrs.
Is DEFBIND(OPEN) parameter in my qlocal has impact for incoming messages when one lpar is down due to IPL?
Thanks in advance to those who will reply.
Cheers,
Migz |
The DEFBIND queue attribute comes into play only if the application specifies MQOO_BIND_AS_QDEF.
No, if one LPAR or QMGR becomes unavailable, an app on the remaining QSG QMGR will be able to consume messages.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| hughson |
| Posted: Wed Sep 14, 2022 2:03 am Post subject: |
|
|
Padawan
Joined: 09 May 2013
Posts: 1959
Location: Bay of Plenty, New Zealand
|
If you have an application using MQOO_BIND_AS_Q_DEF (which is the default) and you have a queue with DEFBIND(OPEN), then any messages currently on a transmission queue destined for the queue manager that was chosen at MQOPEN time, will stay on that transmission queue and will not be reassigned to another cluster queue manager when the queue manager is unavailable.
If you want messages to be reassigned to go into the Shared Q via another member of the cluster, then you need to use MQOO_BIND_NOT_FIXED or change the queue to DEFBIND(NOTFIXED)
Cheers,
Morag
_________________
Morag Hughson @MoragHughson
IBM MQ Technical Education Specialist
Get your IBM MQ training here!
MQGem Software |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Wed Sep 14, 2022 5:04 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
More detail is needed here ... to differentiate between MQ clusters and z/OS-only Queue Sharing Groups.
MQ clusters enable a queue (or multiple instances of the same named queue) to be known (not shared) to members of the same MQ cluster. z/OS MQ doesn't alter this.
In a z/OS Parallel Sysplex QSG (Queue Sharing Group), inbound messages for a QSG shared queue are stored in a Coupling Facility structure. A single instance of a destination queue known to the QSG will be visible by all QSG member qmgrs.
The first (fastest) application will MQGET the message from the CF. If the app fails or qmgr fails or the LPAR is IPLd, another instance of the app in the remaining QSG qmgr will get the message.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| 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
|
|
|
|
