Neil, you are right, I simplified my description a little bit.
Regards Hubert > -----Ursprüngliche Nachricht----- > Von: MQSeries List <[email protected]> > Gesendet: 28.11.06 22:08:36 > An: [email protected] > Betreff: Re: Antwort: Re: Antwort: Re: inbound cluster communication > Hi Hubert, > > > I don't quite agree that an MCA can > never have a blank ObjectQMgr. I believe that in a cluster environment, > when BIND(NOTFIXED) is used, a blank ObjectQMgr is transmitted. This is > why cluster gateways work only when BIND(NOTFIXED) is used. > > > Regards, > > Neil Casey > > Lead Technical Specialist, Middleware MQ > Support > > Technology Operations > > National Australia Bank > > > Level 1, 122 Lewis Rd (Tue Thu) > > Tel: +61 (0) 3 9886 2375 | Fax: > +61 (0) 3 9886 2700 | Mob: +61 (0) 408 356 208 > > Pier 4, Level 8, 800 Bourke St (Mon > Wed Fri) > > Tel: +61 (0) 3 8634 2205 | Fax: > +61 (0) 3 8634 3788 | Mob: +61 (0) 408 356 208 > > Email: [EMAIL PROTECTED] > > > > > > Hubert Kleinmanns <[EMAIL PROTECTED]> > > Sent by: MQSeries List <[email protected]> > > > 28/11/2006 18:49 > > > Please respond to > MQSeries List <[email protected]> > > > > To > [email protected] > > cc > > Subject > Re: Antwort: Re: Antwort: Re: inbound > cluster communication > > > > > > > > > Heinz, > > you are right, the resolving of a queue is done by the QMgr. The MCA is > a normal application, which opens a queue. In difference to other, local > connected, applications, a (receiving) MCA cannot have an empty ObjectQMgr > name, because this is extracted from the Xmit header. > > The MCA sends a "queue open request" to the QMgr with ObjectQMgr > and QbjectQ. If the value of the ObjectQMgr is the same as the local QMgr, > the QMgr resolves the open request only to local defined queues. Otherwise > the QMgr resolves the open request to a XmitQ (directly, if a XmitQ with > the name of the target QMgr exists, or indirectly via QMgr alias or cluster > alias). > > Regards > Hubert > > > > > -----Ursprüngliche Nachricht----- > > Von: [EMAIL PROTECTED] > > Gesendet: 27.11.06 21:30:43 > > An: [email protected] > > Betreff: Re: Antwort: Re: Antwort: Re: inbound cluster communication > > Hubert. > > > > I am afraid I did not clearly show what I am really trying to > > emphasize: you say in your last reply that "the MCA tries to > resolve > > the queue on THIS queue manager" and my understanding is that > all this > > 'addressing' is done by the QMgr, not the MCA - the MCA just passes > the > > queue name and queue manager name from the transmission header to > the > > QMgr and let's it do it's magic. > > > > That's my whole point: to distinguish and understand the roles played > > by the MCA and the QMgr. > > > > Regards. > > > > Heinz > > > > Hubert Kleinmanns wrote: > > Heinz, > > not exactly, > > receiving MCAs always get messages, which contain a target QMgr - > which is NOT blank - and a target Q in the Xmit header (otherwise the sending > MCA would have put the message to the DLQ). When the target QMgr is the > same as the QMgr, to which the MCA is connected to, the MCA trys to resolve > the queue on THIS queue manager (the one processing the MQOPEN). > > When the target QMgr is NOT the local QMgr, the MCA trys to find a > way to the target QMgr. If the target QMgr is known as a cluster QMgr, > the message will put to the cluster XmitQ and send to this QMgr. If the > target QMgr is NOT known as a cluster QMgr, MQ will look for a XmitQ, or > QMgr alias which is named like the target QMgr and resolves to a XmitQ, > and the message is put to the XmitQ. If the QMgr alias contains empty RQMNAME > and XMITQ attributes, it is called a cluster alias and resolves to any > QMgr in the cluster, which holsts the target Q of the Xmit header. Then > the message is put to the cluster XmitQ and load-balancing happens. > > In Javier's sample a QMgr in the cluster (not the QGATEWAY) filled > into the Xmit header would direct the message to this specific QMgr in > the cluster - no load-balancing. The QMgr alias (or cluster alias) ANY > is NOT the LOCAL QMgr, so MQ now resolves to the cluster alias and to any > Qs named like the target Q in the Xmit header. > > Regards > > Hubert > > > > > > -----Ursprüngliche Nachricht----- > > Von: [EMAIL PROTECTED] > > Gesendet: 21.11.06 18:07:01 > > An: [email protected] > > Betreff: Re: Antwort: Re: Antwort: Re: inbound cluster communication > > > > > > > > Hubert. > > > > > > Please allow me to rephrase your explanation, both to check > if I really > > understood what happens and, if I did understand, to describe in more > > details what happens. > > Actually the MCA extracts data from the transmission header to prepare > > the Object Descriptor (MQOD) to open the target queue: queue name > > (ObjectName) and queue manager name (ObjectQMgrName). And here is > where > > the cluster queue is ignored: according to the Application Programming > > Reference manual, if ObjectQMgrName is blank, the cluster queue name > > resolution Javier expected would take place. As this is not the case > > (ObjectQMgrName contains the name of the local queue manager) WMQ > will > > want to open a queue on THIS queue manager (the one processing the > > MQOPEN). > > Is this correct? > > Heinz Klein > > OLTP Tecnologia & Solucoes Ltda. > > Sao Paulo/SP - Brasil > > Hubert Kleinmanns wrote: > > Javier, > > the MCA first looks into the transmission header of the incoming message. > This header is created via a remote q on your non-cluster QMgr and contains > a target QMgr and a target q. The MCA first checks the target QMgr. If > this name is the same as the QMgr to which the MCA is connected, it looks > for a LOCAL defined queue (not cluster queues). If the target QMgr is not > the same as the connected QMgr, the MCA looks for an object, which is named > like the queue MANAGER. This object may be a transmission queue, a QMgr > alias or a cluster alias. Then the MCA opens the corresponding transmission > queue, and put the message to this transmission queue. > > Regards > > Hubert > > > > > > > > > > > > -- > Hubert Kleinmanns > Beratung / Schulung / Projektleitung > > Tel.: +49 (0) 60 78 / 7 12 21 > Fax: +49 (0) 60 78 / 7 12 25 > Mobil: +49 (0) 178 / 6 97 22 54 > > 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 > > > National Australia Bank Ltd - ABN 12 004 044 937 > This email may contain confidential information. If you are not the intended > recipient, please immediately notify us at [EMAIL PROTECTED] or by replying > to the sender, and then destroy all copies of this email. Except where this > email indicates otherwise, views expressed in this email are those of the > sender and not of National Australia Bank Ltd. Advice in this email does not > take account of your objectives, financial situation, or needs. It is > important for you to consider these matters and, if the e-mail refers to a > product(s), you should read the relevant Product Disclosure > Statement(s)/other disclosure document(s) before making any decisions. If you > do not want email marketing from us in future, forward this email with > "unsubscribe" in the subject line to [EMAIL PROTECTED] in order to stop > marketing emails from this sender. National Australia Bank Ltd does not > represent that this email is free of errors, viruses or interference. > > > > ----------------------------------------------------------------- > 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 > -- Hubert Kleinmanns Beratung / Schulung / Projektleitung Tel.: +49 (0) 60 78 / 7 12 21 Fax: +49 (0) 60 78 / 7 12 25 Mobil: +49 (0) 178 / 6 97 22 54 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
