Re: Cluster Problem
With my experience with cluster, Issue REFRESH CLUSTER and wait. It usually, works. MQ takes time to propagate the information. Thanks, AkBar E. Dar The United Illuminating Company New Haven, CT Off: (203) 499-5981 Cell: (203) 623-9270 "Potkay, Peter M (ISD, IT)" To: [EMAIL PROTECTED] <[EMAIL PROTECTED]cc: RTFORD.COM>Subject: Re: Cluster Problem Sent by: MQSeries List <[EMAIL PROTECTED] AC.AT> 11/17/2004 08:52 AM Please respond to MQSeries List Yes, a Full Repo can host clustered queues. If question below is based on "errors" you are seeing from MQExplorer, ignore them. Ignore most everything that MQExplorer tells you related to errors with Clusters. Verify it with commands from runmqsc before worrying about it. -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Jay Lang Sent: Tuesday, November 16, 2004 4:26 PM To: [EMAIL PROTECTED] Subject: Cluster Problem I have created a cluster on a server having the two repository QM's on the same server. When I try to create a Q on one of the repo QM's, it does not show a cluster available to share the queue in. Can a repo QM have a cluster queue? I can create another QM on the same server, join the cluster, and create a cluster Q, no problem. -- Jay H. Lang Chief Technologist Distributed Computing Professionals Inc. IBM Certified Specialist - WebSphere MQ 303 277-1873 - Colorado Office 651 406-2131 - USPS Office 303 807-9700 - Cell This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential 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 email and delete this communication and destroy all copies. - This e-mail, and any attached file(s), is intended solely for the use of the individual or entity to whom this e-mail is addressed and may contain information that is privileged, confidential or exempt from disclosure. If you are not one of the named recipient(s) or otherwise have reason to believe that you have received this message in error, please notify the UI Information Security Manager at 203-499-3689 and delete this message immediately from any computer. Any other use, retention, dissemination, retransmission, printing or copying of this e-mail is strictly prohibited. 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: Moving Queue Manager to New Server
I am not duplicating the Queue Manger, rather we moving to a new machine. Once New machine is imaged, I will turn off the other machine and configure the same Queue Manager on the New machine with the information like Server Name(CONNAME) and reset the Channel Sequence Number. Then run the security file(was created using "amqoamd") back in with the updated security information. This should get the Queue Manager running in a Cluster under the new location. Bill; I did find the Channel information, once I ran the "saveqmgr" but cluster definition is not there. I don't think there is anything else. Let me know if I am missing anything. Thanks, (Embedded image moved to file: pic02306.gif) - This e-mail, and any attached file(s), is intended solely for the use of the individual or entity to whom this e-mail is addressed and may contain information that is privileged, confidential or exempt from disclosure. If you are not one of the named recipient(s) or otherwise have reason to believe that you have received this message in error, please notify the UI Information Security Manager at 203-499-3689 and delete this message immediately from any computer. Any other use, retention, dissemination, retransmission, printing or copying of this e-mail is strictly prohibited. <>
Moving Queue Manager to New Server
Hi: We are moving One of our Queue Manager in the Cluster to a New Machine. I have downloaded MS03 SupportPac(saveqmgr) to copy the Queue definitions and "amqoamd" to copy over the Security information. I am wondering that Is there way of creating the Channel and Cluster information to a Script file, editing that script file with the New server information then implementing it to the New Queue Manger? This would make the process less manual. Thanks, (Embedded image moved to file: pic19264.gif) - This e-mail, and any attached file(s), is intended solely for the use of the individual or entity to whom this e-mail is addressed and may contain information that is privileged, confidential or exempt from disclosure. If you are not one of the named recipient(s) or otherwise have reason to believe that you have received this message in error, please notify the UI Information Security Manager at 203-499-3689 and delete this message immediately from any computer. Any other use, retention, dissemination, retransmission, printing or copying of this e-mail is strictly prohibited. <>
Re: Moving to a New Machine
OK, I knew that I would forget the to mention the environment. We are moving to new Windows NT machine. And, By the Way, we have circular logging( I know the recovery is difficult with it). (Embedded image moved to file: pic25477.gif) Akbar Dar To: [EMAIL PROTECTED] 06/30/2004 01:25 cc: [EMAIL PROTECTED] PM Subject: Moving to a New Machine Hi: We have to move to new server where we have MQ SERIES loaded. In this move I/P address is also going to change. We have Two Queue Manger defined on this machine, and these Queue Managers have Regular, Alias(part of a cluster), and Cluster Queue defined. I would appreciate if you folks can give me running start in regarding: 1. Installing vs. copying the MQ Series Binaries 2. Redefining the Queue Managers and the Queues Thanks in Advance. (Embedded image moved to file: pic22998.gif) - This e-mail, and any attached file(s), is intended solely for the use of the individual or entity to whom this e-mail is addressed and may contain information that is privileged, confidential or exempt from disclosure. If you are not one of the named recipient(s) or otherwise have reason to believe that you have received this message in error, please notify the UI Information Security Manager at 203-499-3689 and delete this message immediately from any computer. Any other use, retention, dissemination, retransmission, printing or copying of this e-mail is strictly prohibited. <><>
Moving to a New Machine
Hi: We have to move to new server where we have MQ SERIES loaded. In this move I/P address is also going to change. We have Two Queue Manger defined on this machine, and these Queue Managers have Regular, Alias(part of a cluster), and Cluster Queue defined. I would appreciate if you folks can give me running start in regarding: 1. Installing vs. copying the MQ Series Binaries 2. Redefining the Queue Managers and the Queues Thanks in Advance. (Embedded image moved to file: pic26299.gif) - This e-mail, and any attached file(s), is intended solely for the use of the individual or entity to whom this e-mail is addressed and may contain information that is privileged, confidential or exempt from disclosure. If you are not one of the named recipient(s) or otherwise have reason to believe that you have received this message in error, please notify the UI Information Security Manager at 203-499-3689 and delete this message immediately from any computer. Any other use, retention, dissemination, retransmission, printing or copying of this e-mail is strictly prohibited. <>
R3 Link related Queue
We are using WMQ 5.3 with CSD04. We have four Queue Managers(3 on NT and one on AIX Unix) defined in a Cluster environment. And, One of NT Queue Manger is connected to SAP via R3 Link. It works fine, but sometime, SAP cannot put a message on the R3 Link Queue and we get a Reason Code 2085. In order to fix this error, I "Refresh Cluster Information" and problem goes away and R3 Link related Queue starts to work fine. I have been told by IBM that Cache information gets corrupted and once refreshed, it works and they recommended latest CSD06. Has anybody experienced this problem and would the latest CSD fix it? Thanks, AkBar Dar IT Technical Administrator United Illuminating New Haven, CT - This e-mail, and any attached file(s), is intended solely for the use of the individual or entity to whom this e-mail is addressed and may contain information that is privileged, confidential or exempt from disclosure. If you are not one of the named recipient(s) or otherwise have reason to believe that you have received this message in error, please notify the UI Information Security Manager at 203-499-3689 and delete this message immediately from any computer. Any other use, retention, dissemination, retransmission, printing or copying of this e-mail is strictly prohibited. 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
R3 Link related Queue
We are using WMQ 5.3 with CSD04. We have four Queue Managers(3 on NT and one on AIX Unix) defined in a Cluster environment. And, One of NT Queue Manger is connected to SAP via R3 Link. It works fine, but sometime, SAP cannot put a message on the R3 Link Queue and we get a Reason Code 2085. In order to fix this error, I "Refresh Cluster Information" and problem goes away and R3 Link related Queue starts to work fine. I have been told by IBM that Cache information gets corrupted and once refreshed, it works and they recommended latest CSD06. Has anybody experienced this problem and would the latest CSD fix it? Thanks, AkBar Dar IT Technical Administrator United Illuminating New Haven, CT - This e-mail, and any attached file(s), is intended solely for the use of the individual or entity to whom this e-mail is addressed and may contain information that is privileged, confidential or exempt from disclosure. If you are not one of the named recipient(s) or otherwise have reason to believe that you have received this message in error, please notify the UI Information Security Manager at 203-499-3689 and delete this message immediately from any computer. Any other use, retention, dissemination, retransmission, printing or copying of this e-mail is strictly prohibited. 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