I think, shared channels in a queue sharing group work this way, but these ara only available on z/OS. You need a queue sharing group therefor.
Possible you could use two gateways and overlapping clusters. Another issue are MQ-Clients. They have two connect to one specific QMgr. Maybe IBM could add a CONNAMNL (CONNAME namelist) and clients you choose one from the defined connections ... Regards Hubert > -----Ursprüngliche Nachricht----- > Von: MQSeries List <[email protected]> > Gesendet: 13.02.08 14:45:59 > An: [email protected] > Betreff: Re: Wish List for the next version of MQ > Bobbee, what you are thinking of is that of MQ 6.0 you no longer need to > connect to a QM that didn't host your clustered q to achieve round robining. > In MQ 5.3 and earlier a local instance of the clustered q would grab all > MQPUTs. > > > > What Tim is asking for is related to conventional SNDR channels coming into > the cluster. This is usually done to a single QM in the cluster, the gateway. > The problem is that gateway QM becomes a single point of failure. Yes, you > can mitigate that with hardware clustering but you still have a slight > vulnerability that the hardware clustering could fail and you have downtime > during a failover when the failover from Node 1 to Node 2 does work. The > single gateway QM is also a potential performance bottleneck. He wants to be > able to specify one string as the "hostname" in a SNDR channel's definition > (from a QM outside the cluster), and have that resolve somehow to anyone of > the QMs in the cluster. At that point anyone of them becomes the gateway. I > would say the need exists for anyone that has regular QMs needing to talk to > clustered QMs. I have a gateway QM. Its the busiest QM in the company when > you look at total # of messages passing thru. It would be very bad if the > hardware clustering somehow failed and that QM was N/A. > > > > Its almost like a Client Channel Table for QM to QM connections. A QM Channel > Table. Hmmmmmmmmmmm......... > > > > > > > > > Peter Potkay > > > > ----------------------------------------------------------------- > From: MQSeries List [mailto:[EMAIL PROTECTED] On Behalf Of Robert Broderick > Sent: Wednesday, February 13, 2008 5:49 AM > To: [email protected] > Subject: Re: Wish List for the next version of MQ > > > Hi Tim, > I am tracking these. Could you expand on this. I thought the need for a > Gateway was eliminated in v6. I would think I am missing your need as that is > probably not what you are talking about. I want to understand my > mis-interpeditation. > > bobbee > > > > > > ----------------------------------------------------------------- > > > Date: Wed, 13 Feb 2008 10:14:50 +0000 > > From: [EMAIL PROTECTED] > > Subject: Re: Wish List for the next version of MQ > > To: [email protected] > > > > After working on a project for a large retailer, could I add the > > requirement to be able to connect to a cluster without having to go > > through a gateway queue manager? > > > > A definition to connect to the cluster would be on the lines of the > > following: > > > > DEFINE CHANNEL(T1.CLUSTER) Conname('cluster address') > > > > This would provide the ability for multipe queue managers within the > > cluster to be able to share the listening workload. > > > > Regards, > > > > Tim Crossland > > > > -----Original Message----- > > From: MQSeries List [mailto:[EMAIL PROTECTED] On > > Behalf Of Meekin, Paul > > Sent: 13 February 2008 08:33 > > To: [email protected] > > Subject: Re: Wish List for the next version of MQ > > > > (Sorry - thought I'd sent this earlier - still, better late than never!) > > > > That reminds me of another one: > > > > - An API to allow Channel Exits to put messages to the AMQERR01.LOG > > file. > > > > Cheers, > > Paul > > > > > > -----Original Message----- > > From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf > > Of T-Rob > > Sent: 08 February 2008 16:17 > > To: [email protected] > > Subject: Re: Wish List for the next version of MQ > > > > > > One more to add to this list... > > > > How about adding a comment field to endmqm? The comment would then be > > recorded into the log files. > > > > endmqm -i MYQMGR -c "Applying maintenance - FP 6.0.2.3" > > endmqm -i MYQMGR -c "Testing HA Failover" > > endmqm -i MYQMGR -c "Shutting down for decommission - DO NOT RESTART!!!" > > > > Then if someone looked in the log files this comment would be toward the > > end. Shutdown scripts would embed a similar comment "QMgr shut down by > > the system". There would be a new AMQ????? message code that > > essentially said "user supplied message". > > > > This one's so easy can we maybe get it in the next fix pack? > > > > -- T.Rob > > > > To unsubscribe, write to [EMAIL PROTECTED] and, in the > > message body (not the subject), write: SIGNOFF MQSERIES 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 > > > > To unsubscribe, write to [EMAIL PROTECTED] and, in the > > message body (not the subject), write: SIGNOFF MQSERIES 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 > > > > > > This message has been scanned by MailController - > > www.MailController.altohiway.com > > > > To unsubscribe, write to [EMAIL PROTECTED] and, > > in the message body (not the subject), write: SIGNOFF MQSERIES > > 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 > > > > ----------------------------------------------------------------- > Helping your favorite cause is as easy as instant messaging. You IM, we give. > Learn more. > > ----------------------------------------------------------------- > List Archive - Manage Your List Settings - Unsubscribe > > > Instructions for managing your mailing list subscription are provided in the > Listserv General Users Guide available at http://www.lsoft.com > > ************************************************************************* > This communication, including attachments, is > for the exclusive use of addressee and may contain proprietary, > confidential and/or privileged information. If you are not the intended > recipient, any use, copying, disclosure, dissemination or distribution is > strictly prohibited. If you are not the intended recipient, please notify > the sender immediately by return e-mail, delete this communication and > destroy all copies. > ************************************************************************* > -- Hubert Kleinmanns Beratung / Schulung / Projektleitung Chairman der WG "WebSphere MQ and Business Integration" in der GSE, deutsche Region. Tel.: +49 (0) 60 78 / 7 12 21 Fax: +49 (0) 60 78 / 7 12 25 Mobil: +49 (0) 178 / 6 97 22 54 Web: www.kleinmanns.eu GSE: www.gsenet.de To unsubscribe, write to [EMAIL PROTECTED] and, in the message body (not the subject), write: SIGNOFF MQSERIES 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
