Hi Peter, I agree that in my experience, alphabetical order has always worked, and I have designed systems in the past which relied on this.
However, when I was researching my response to the original question, I found the following statement in the Application Programming Reference, in the area talking about the QMgrName parameter of the MQCONN call. "MQ client queue-manager groups: If the specified name starts with an asterisk (*), the queue manager to which connection is made might have a different name from that specified by the application. The specified name (without the asterisk) defines a group of queue managers that are eligible for connection. The implementation selects one from the group by trying each one in turn (in no defined order) until one is found to which a connection can be made. If none of the queue managers in the group is available for connection, the call fails. Each queue manager is tried once only. If an asterisk alone is specified for the name, an implementation-defined default queue-manager group is used." This specifically says that the search is performed in "no defined order". I believe that IBM are ensuring that if they find a more efficient way to implement this function in future, and change the order, customer can't complain. I was trying to avoid making a statement which could cause problems in the future if IBM ever changed this area of code. Regards, Neil C. ____________________________________________________________________________________________________________ Neil Casey| Lead Technical Specialist - Systems Management Group | Atlas Technology Services | nabCapital™ | A division of National Australia Bank Limited Office: +61 3 8641 1068 | Mobile: 0438 573 152 | Fax: +61 3 8641 4699 | Email: [EMAIL PROTECTED]| Location: Level 24, 500 Bourke Street, Melbourne Intranet Portal: http://intranet.global.thenational.com/Units/Services/Technology/ATLAS/AppSer/SysMan/Pages/default.aspx "Potkay, Peter M (ISD, IT)" <[EMAIL PROTECTED] To HARTFORD.COM> MQSERIES@LISTSERV.MEDUNIWIEN.AC.AT Sent by: MQSeries cc List <[EMAIL PROTECTED] Subject V.MEDUNIWIEN.AC.A Re: CCDT in WAS6 T> 03/20/2008 12:32 AM Please respond to MQSeries List <[EMAIL PROTECTED] V.MEDUNIWIEN.AC.A T> Neil, I don't know if WAS puts a different spin on it, but in base MQ the client channel table is always searched alphabetically by channel name, so in the below example the app would always attempt connect to host1 and only try host2 if communication could not be established to host1, because the channel name to host1 is alphabetically ahead of the channel to host2. Peter Potkay -----Original Message----- From: MQSeries List [mailto:[EMAIL PROTECTED] On Behalf Of Neil Casey Sent: Tuesday, March 18, 2008 5:34 PM To: MQSERIES@LISTSERV.MEDUNIWIEN.AC.AT Subject: Re: CCDT in WAS6 Hi Srini, I found this bit of the client interface confusing as well at first. At an initial look, the use of asterisk makes it look like a generic match string, but it isn't. As it turns out, you cannot search for a generic queue manager name matching in the client channel table. The '*' is an indicator that the name the follows is a "Client Queue Manager Group" name. This means that the channel table is searched for all entries with that name (without the asterisk), and that the actual queue manager name is allowed to be different to the group name. This allows your code to access one of several queue managers, depending on what is available at the time. So, if you had QM1 at host1(1414) and QM2 at lost2(1415) You could define a channel table like DEFINE CHL(CLIENT.TO.QM1) chltype(clntconn) conname('host1(1414)') trptype(tcp) qmname(QMGROUP) and DEFINE CHL(CLIENT.TO.QM2) chltype(clntconn) conname('host2(1415)') trptype(tcp) qmname(QMGROUP) You application can now use the resultant channel table, and issue MQCONN("*QMGROUP",hconn,ccode,rcode) In your QCF, you specify "*QMGROUP" as the queue manager name, along with the client channel table information. You will get a connection to one of the two queue managers. MQ does not guarantee which queue manager will receive the connection request first, so even if both QMs are up, you could end up with a connection to either one. Regards, Neil C. ________________________________________________________________________ ____________________________________ Neil Casey| Lead Technical Specialist - Systems Management Group | Atlas Technology Services | nabCapital(tm) | A division of National Australia Bank Limited Office: +61 3 8641 1068 | Mobile: 0438 573 152 | Fax: +61 3 8641 4699 | Email: [EMAIL PROTECTED]| Location: Level 24, 500 Bourke Street, Melbourne Intranet Portal: http://intranet.global.thenational.com/Units/Services/Technology/ATLAS/A ppSer/SysMan/Pages/default.aspx Srinivas Manepalli <Srinivas.Manepal To [EMAIL PROTECTED] MQSERIES@LISTSERV.MEDUNIWIEN.AC.AT S.COM> cc Sent by: MQSeries List Subject <[EMAIL PROTECTED] CCDT in WAS6 V.MEDUNIWIEN.AC.A T> 03/19/2008 07:29 AM Please respond to MQSeries List <[EMAIL PROTECTED] V.MEDUNIWIEN.AC.A T> This is my first post. I am trying to set CCDT in WAS6.1 for qmgr failover thorugh MQ queue connection factory. I read that we can give the qmgr searh string as 'qmgr*' to search the qmgr starting with name 'qmgr'. but WAS is not recognizing '*'. If I leave the QMGR name as blank it is looking for the default QMGR. am I doing it wrong? or is it only configured through coding? If anybody have setup CCDT thorugh WAS QCF please share your experience. I would really appreciate. Thanks, Srini. -----Original Message----- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Konczak, Tony (Dublin) Sent: Tuesday, March 18, 2008 3:15 PM To: MQSERIES@LISTSERV.MEDUNIWIEN.AC.AT Subject: Re: BSDS / Logging datasets rename Have you tried REPRO'ing the old BSDS to the new BSDS name and the old LOGS to the new LOGS? That put's everything back in your newly named BSDS/LOGS. Tony Konczak Database Administrator - Senior, ETBS Checkfree - now part of Fiserv Phone: 614.564.4359 Mobile: 614.571.5404 Fax: 614.564.4659 http://www.checkfree.com From: MQSeries List [mailto:[EMAIL PROTECTED] On Behalf Of Doug Clark Sent: Tuesday, March 18, 2008 1:16 PM To: MQSERIES@LISTSERV.MEDUNIWIEN.AC.AT Subject: BSDS / Logging datasets rename I have to rename the BSDS and logging datasets to conform to new naming convention standards. The pageset datasets were already renamed. What I have done is to create a new BSDS and logging files but when I start the queue manager I receive an error indicating that the queue manager pasgeset was out of sync with the BSDS and logging datasets. Is there a process show the steps to rename the BSDS and logging datasets anywhere? Thanks, Doug _____ List Archive <http://listserv.meduniwien.ac.at/archives/mqser-l.html> - Manage <http://listserv.meduniwien.ac.at/cgi-bin/wa?SUBED1=mqser-l&A=1> Your List Settings - Unsubscribe < mailto:[EMAIL PROTECTED]&BODY=signo ff%20mqseries > Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com < http://www.lsoft.com/resources/manuals.asp> _____ List Archive <http://listserv.meduniwien.ac.at/archives/mqser-l.html> - Manage <http://listserv.meduniwien.ac.at/cgi-bin/wa?SUBED1=mqser-l&A=1> Your List Settings - Unsubscribe < mailto:[EMAIL PROTECTED]&BODY=signo ff%20mqseries > Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com < http://www.lsoft.com/resources/manuals.asp> The information contained in this message and any attachment may be proprietary, confidential, and privileged or subject to the work product doctrine and thus protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify me immediately by replying to this message and deleting it and all copies and backups thereof. Thank you. 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. ************************************************************************* 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. ************************************************************************* 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.
