Morag already answered the naming issue, one more hint for the gateway.
one of the advantages of a queue sharing group is availability. queues are available to more than one queuemanager, so if
one goes down others still can process the messages in the shared queue. if you create a gateway queuemanager then you
create a single point of failure. why not use shared inbound channels (and a shared port) to the qsg? so every queuemanager
within the qsg can work as a gateway queuemqanager......
Stefan
| "Criscione, Carol (DIS)"
<[EMAIL PROTECTED]>
Sent by: MQSeries List <[email protected]> 21.10.2005 20:37
|
|
I have a customer who has the same queue names in Test, Quality, Demo, and Production QMgrs (Point-to-Point).
We want to include them in a Shared Queue configuration (comprised of 4 Queue-Sharing Groups.) Does WMQ put a QSG ID or anything else on the queue names to differentiate them in a Coupling Facility? Also, if I use Gateway QMgrs, do I have to have one for each QSG?
Thank you.
Carol Criscione
CICS TS and WMQ Technical Services
Dept. of Information Services
Group: [EMAIL PROTECTED]
Group: (360) 902-3194
[EMAIL PROTECTED]
Instructions for managing your mailing list subscription
are provided in the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html
Diese E-Mail enthaelt vertrauliche oder rechtlich geschuetzte
Informationen.
Wenn Sie nicht der beabsichtigte Empfaenger sind, informieren Sie bitte
sofort den Absender und loeschen Sie diese E-Mail. Das unbefugte
Kopieren
dieser E-Mail oder die unbefugte Weitergabe der enthaltenen
Informationen
ist nicht gestattet.
The information contained in this message is confidential or protected
by
law. If you are not the intended recipient, please contact the sender
and
delete this message. Any unauthorised copying of this message or
unauthorised distribution of the information contained herein is
prohibited.
Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html
