Re: Clustering Question
Title: Message Hi Tony, Have you considered adding clustered aliases to your TEST.QUEUE's, e.g. PARTICULAR.TEST.QUEUE. That way your consumers canget their messages from a single queue, even when the producer wanted a particular destination. It also gives you the option of scaling up a location or region's resources by having multiple aliases with the same name. You also get the opportunity of naming the aliases with qualifiers that are meaningful in business terms, rather than MQ admin terms. It is also clean JMS. Alan -Original Message-From: MQSeries List [mailto:[EMAIL PROTECTED] On Behalf Of Wyatt, T RobSent: 29 November 2004 17:29To: [EMAIL PROTECTED]Subject: Re: Clustering Question Funny but we just had this conversation in our team meeting today except it was about JMS and Pub/Sub. My colleague was explaining that JMS requires a one-to-one correspondence between JNDI managed objects and potential destinations.So a cluster queue defined in JNDIis known to JMS as a single destination, no matter how many instances of the queue exist. OR...you can have a different JNDI object for each combination of QMgr/Queue, even though the queues all have the same name. What you cannot do, apparently, is open a JNDI object and dynamically specify the QMgr part of the destination because "QMgr" is an MQ constructis not part of the JMS spec. So if my colleague is correct (and we are still pretty new to JMS over here so I'll be the first to admit this may be a much deeper issue), you either need to create a separateJNDI object for each possible destination queue, or use a solution that is not pure JMS. I'll be interested to see if anyone else has a solution that works within JMS and does not require all the JNDI objectsbecause it might help us with our Pub/Sub problem. -- T.Rob -Original Message-From: MQSeries List [mailto:[EMAIL PROTECTED]On Behalf Of Bender, AlanSent: Monday, November 29, 2004 11:44 AMTo: [EMAIL PROTECTED]Subject: Re: Clustering Question Sorry, I made a poor assumption, I should know better. We may do it differently than Tony has in mind. Our online app is on the WAS server and we always connect to the same QMGR with JMS. Then based on customer number, or some other factor that determines where an order is filled we send the Queue messages to the correct queue. It is at that point we require a unique queue name as any reference to the receiving queue manager name in the message header will, no can but will, cause the 2085 error message. I don't understand your reference to round robining as the original question asked about sending a message to a unique queue. Alan From: MQSeries List [mailto:[EMAIL PROTECTED] On Behalf Of Potkay, Peter M (ISD, IT)Sent: Monday, November 29, 2004 10:24 AMTo: [EMAIL PROTECTED]Subject: Re: Clustering Question You should use the QMGR name attribute of the queue object, and populate it with the name of a QM in the cluster that does host the queue. If you choose a QM that does not have the queue, you will get the 2085. If you populate it with the local QM name, you lose round robining if the local QM hosts that queue, or 2085 if it does not. You don't need to make different q names on all your clustered QMs. -Original Message-From: MQSeries List [mailto:[EMAIL PROTECTED]On Behalf Of Bender, AlanSent: Monday, November 29, 2004 11:17 AMTo: [EMAIL PROTECTED]Subject: Re: Clustering Question Tony, We have an application running with the same component versions. You must remember that in a cluster containing multiple copies of the same Queue name the cluster will load balance. We have also noted that with the JMS client connection if the QMGR name is used in the JMS configuration we get the dreaded 2085 error code MQRC_UNKNOWN_OBJECT_NAME. What we have done is to append the Queue name with the, in our case, division number. (example: TEST.QUEUE.012). That way you have a unique queue. This may seem simplistic but it does work. Alan From: MQSeries List [mailto:[EMAIL PROTECTED] On Behalf Of Tony.AllisonSent: Monday, November 29, 2004 9:53 AMTo: [EMAIL PROTECTED]Subject: Clustering Question Good morning everyone... I think I am having a brain meltdown Here is what we are trying to accomplish. Components:1. WAS 5.1 2. Websphere MQ 5.3.0.8 1370 queue managers in single cluster. WAS application running with client connection to central queue manager needs to send a single message to one queue manager in the
Help on Candle Management Workstation
Hello everyone, I've just installed Candle Management Workstation on my Windows machine but am having trouble configuring this. I've never used Candle before. The initial screen prompts for a user-id and password. Is this referring to the MQSeries user ? There's a tab called CMS Location Broker, what do i add here? Anyone done this before? Thanks, Samuel ___ ALL-NEW Yahoo! Messenger - all new features - even more fun! http://uk.messenger.yahoo.com Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: APAR for Routing Problem using QM Alias
A couple of APARs to examine would be PQ74736 and PQ87649. -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] On Behalf Of K K Sent: Tuesday, November 30, 2004 7:06 AM To: [EMAIL PROTECTED] Subject: APAR for Routing Problem using QM Alias Dear MQer, I heard that there is an APAR for WMQ for z/OS that cause intermittent failure in routed reply messages using QM Alias. If you know, would you advise the APAR number for me to collect more information on the impact. TIA _ %21~'^!B6:q!B$p,P,P... v:)9aAn 1!$_3sC4 http://us.rd.yahoo.com/evt=22281/*http://ringtone.yahoo.com.hk/ Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive - This e-mail message and any attachments contain confidential information from Medco. If you are not the intended recipient, you are hereby notified that disclosure, printing, copying, distribution, or the taking of any action in reliance on the contents of this electronic information is strictly prohibited. If you have received this e-mail message in error, please immediately notify the sender by reply message and then delete the electronic message and any attachments. Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: Help on Candle Management Workstation
The CMS Location Broker tab is there for all of the connection information for the CMS: the IP address, the remote LU, etc. Mike Davidson TSYS MQ Tech Support [EMAIL PROTECTED] W Samuel [EMAIL PROTECTED] Sent by: MQSeries List [EMAIL PROTECTED] 11/30/2004 06:41 AM Please respond to MQSeries List To:[EMAIL PROTECTED] cc: Subject:Help on Candle Management Workstation Hello everyone, I've just installed Candle Management Workstation on my Windows machine but am having trouble configuring this. I've never used Candle before. The initial screen prompts for a user-id and password. Is this referring to the MQSeries user ? There's a tab called CMS Location Broker, what do i add here? Anyone done this before? Thanks, Samuel ___ ALL-NEW Yahoo! Messenger - all new features - even more fun! http://uk.messenger.yahoo.com Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive The information contained in this communication (including any attachments hereto) is confidential and is intended solely for the personal and confidential use of the individual or entity to whom it is addressed. The information may also constitute a legally privileged confidential communication. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this communication in error and that any review, dissemination, copying, or unauthorized use of this information, or the taking of any action in reliance on the contents of this information is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail, and delete the original message. Thank you
Re: Help on Candle Management Workstation
Samuel, The UID and PW should be your normal mainframe ones; the same ones you'd use for the ISPF MQ panels. The CMS Location Broker is the IP address of your CMS (usually a started task on the mainframe). Ò¿Ó Bob Juch Citigroup MQ Mainframe Support Team Weehawken, NJ 201-974-2147 mailto:[EMAIL PROTECTED] -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of W Samuel Sent: Tuesday, November 30, 2004 6:42 AM To: [EMAIL PROTECTED] Subject: Help on Candle Management Workstation Hello everyone, I've just installed Candle Management Workstation on my Windows machine but am having trouble configuring this. I've never used Candle before. The initial screen prompts for a user-id and password. Is this referring to the MQSeries user ? There's a tab called CMS Location Broker, what do i add here? Anyone done this before? Thanks, Samuel Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: Help on Candle Management Workstation
It depends on where your CMS is located. If it's on the mainframe, it would be your TSO userid and password. If it's on a distributed platform, I would assume it would be the userid and password on that platforms. W Samuel [EMAIL PROTECTED] Sent by: MQSeries List [EMAIL PROTECTED] 11/30/2004 06:41 AM Please respond to MQSeries List [EMAIL PROTECTED] To [EMAIL PROTECTED] cc Subject Help on Candle Management Workstation Hello everyone, I've just installed Candle Management Workstation on my Windows machine but am having trouble configuring this. I've never used Candle before. The initial screen prompts for a user-id and password. Is this referring to the MQSeries user ? There's a tab called CMS Location Broker, what do i add here? Anyone done this before? Thanks, Samuel ___ ALL-NEW Yahoo! Messenger - all new features - even more fun! http://uk.messenger.yahoo.com Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Version 5.3.4 of MO71 available
Version 5.3.4 of my Administrator SupportPac is now available on the SupportPac WebSite. http://www-1.ibm.com/support/docview.wss?rs=203uid=swg24000142loc=en_UScs=utf-8lang=en My thanks to many of you who have helped with suggestions and/or bug reports. Cheers, P. Paul G Clarke WebSphere Messaging Clients IBM Hursley Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: Help on Candle Management Workstation
Samuel, The default startup ID is SYSADMIN with no password required. Make sure when you customized the CMS that you did not turn on Security Validation. Once you log in with the SYSADMIN ID you can setup other users and then re-customize the CMS to perform Security Validation, which will cause the CMS to check the ID and password against the OS where the CMS is installed. Barry W Samuel [EMAIL PROTECTED] CO.UK To Sent by: MQSeries [EMAIL PROTECTED] List cc [EMAIL PROTECTED] N.AC.AT Subject Help on Candle Management Workstation 11/30/2004 06:41 AM Please respond to MQSeries List Hello everyone, I've just installed Candle Management Workstation on my Windows machine but am having trouble configuring this. I've never used Candle before. The initial screen prompts for a user-id and password. Is this referring to the MQSeries user ? There's a tab called CMS Location Broker, what do i add here? Anyone done this before? Thanks, Samuel ___ ALL-NEW Yahoo! Messenger - all new features - even more fun! http://uk.messenger.yahoo.com Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Ben Walker
I will be out of the office starting 29/01/2004 and will not return until 31/12/2005. I have now left HBOS. Please can you redirect your request to $GTDistributedMidd[EMAIL PROTECTED] Thanks and all the best, Ben. -- -- HBOS plc, Registered in Scotland No. SC218813. Registered Office: The Mound, Edinburgh EH1 1YZ. HBOS plc is a holding company, subsidiaries of which are authorised and regulated by the Financial Services Authority. == Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive