Paul, Just curious - I thought the direction was to use the QMID rather than the QMgr name. Is this not the case with channel status info as described below?
Thanks -- T.Rob -----Original Message----- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Paul Clarke Sent: Friday, June 25, 2004 7:38 AM To: [EMAIL PROTECTED] Subject: Re: FW: MQ Administration query Yvette, I'm afraid my answers to Bharath questions would have been somewhat different. Scenario 1 : When you repoint your sender chl connectivity to a different machine. Currently, the remote Q Mgr is not running. Would a reset on my sender chl make an impact in the receiver chl, if do a reset now (Remember the Remote Q Mgr is not running) and bring up the remote Q Mgr later. Answer: If you issue a RESET CHANNEL on a Sender it will have no effect until the channel actually starts. When it does, the RESET will happen on the receiver after any indoubt transactions are resolved but before any messages are transferred. A RESET on the Sender end only should be sufficient (it should not be necessary to issue a RESET on a receiver unless you're using an old or odd QM). The receiver channel should switch to whatever sequence number the sender has been reset to. In an ideal world one would never have to ever issue a RESET on a receiver. Scenario 2: Ideally you would like every sender to possess a corresponding receiver. Now in our scenario, we have 1 receiver in my Q Mgr listening to 3 sender chls from 3 different Q Mgrs. Now how would a reset operation in one of the sender chls impact the receiver or other sender chls? Also, how does the Seq numbers become now in all the Q Mgrs. Answer: It is perfectly reasonable and often desirable to have a single receiver channel definition receiving messages from many different Queue Managers. The sequence number is maintained per remote partner. If you do a DIS CHS(*) SAVED you'll see many entries for the same channel but with different CONNAMEs. Note that CONNAME may be the machine address or more likely nowadays the remote Queue Manager name. When you're using 'generic' receivers like this issuing a RESET CHANNEL on the receiver is non-deterministic because MQ doesn't know which instance of the receiver channel you're intending. In fact it's a race. The first receiver channel to start with get the new sequence number. This is another reason why we recommend you don't issue RESET channel on receivers. However, in this environment issuing RESET on the senders is perfectly fine because, as I said, we maintain a completely separate record for each Sender/Reciver pair. Therefore issuing RESET on one sender/receiver pair should have no effect on any other sender/receiver pair. Of course, this is assuming that each sender is running on a Queue Mangager with a different name but then no one would be daft enough to define two (or more) different Queue Managers in their network with the same Queue Manager name right ? :-) Cheers, P. Paul G Clarke WebSphere MQ Development IBM Hursley "Carroll, Y. (Yvette)" <[EMAIL PROTECTED] To OM> [EMAIL PROTECTED] Sent by: MQSeries cc List <[EMAIL PROTECTED] Subject N.AC.AT> FW: MQ Administration query 25/06/2004 12:05 Please respond to MQSeries List Hi Bharath Scenario 1: A reset on the side of the sender channel while your receiving qmgr is down will not affect the receiving side until the receiving side comes up. Then you just need to ensure that the sequence numbers at both sides of the channel are the same. Scenario 2: Assuming you're talking qmgr to qmgr: Why would you want to point 3 different sender channels at the same receiver? Only one sender would ever be able to be up at the same time. And when sender 2 attempt to start, the sequence numbers would almost be guaranteed to be out since the receiver was synced with sender 1. My suggestion would be to have a separate receiver for each sender. Much better and safer. Or are you referring to a client/server scenario? Where 3 server connections are configured, one each from 3 different MQ clients talking to a single MQ server. In that case there are no sequence numbers for you to worry about. Kind regards Yvette Carroll -----Original Message----- From: Bharath Ram Srinivasan [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 23, 2004 4:25 PM Subject: MQ Administration query Folks, Thought I knew what Resetting a chl was all about. But no there is a gap which I would be happy if you could fill. Scenario 1 : When you repoint your sender chl connectivity to a different machine. Currently, the remote Q Mgr is not running. Would a reset on my sender chl make an impact in the receiver chl, if I do a reset now (Remember the Remote Q Mgr is not running) and bring up the remote Q Mgr later. Scenario 2: Ideally you would like every sender to possess a corresponding receiver. Now in our scenario, we have 1 receiver in my Q Mgr listening to 3 sender chls from 3 different Q Mgrs. Now how would a reset operation in one of the sender chls impact the receiver or other sender chls? Also, how does the Seq numbers become now in all the Q Mgrs. Thank You in Advance for your inputs. ~ Bharath This email and any accompanying attachments may contain confidential and proprietary information. This information is private and protected by law and, accordingly, if you are not the intended recipient, you are requested to delete this entire communication immediately and are notified that any disclosure, copying or distribution of or taking any action based on this information is prohibited. Emails cannot be guaranteed to be secure or free of errors or viruses. The sender does not accept any liability or responsibility for any interception, corruption, destruction, loss, late arrival or incompleteness of or tampering or interference with any of the information contained in this email or for its incorrect delivery or non-delivery for whatsoever reason or for its effect on any electronic device of the recipient. If verification of this email or any attachment is required, please request a hard-copy version. (See attached file: InterScan_Disclaimer.txt) 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
