Tom's description is absolutely accurate. [For completeness I might add 3) STOP MODE(FORCE) was used, but it is a little off topic]
Also, I believe Tom IS an IBMer :-) Cheers Morag Morag Hughson WebSphere MQ for z/OS Development Telephone: +44 (0) 1962 816900 Internet: [EMAIL PROTECTED] ------------------------------------------------------ Tom, I was hoping an IBMer would ring in on this one. Thanks Bill Anderson Senior Systems Analyst SITA Atlanta, GA 770-303-3503 (office) 404-915-3190 (cell) [EMAIL PROTECTED] http://www.mconnect.aero/ Tom Schneider <[EMAIL PROTECTED] To: [EMAIL PROTECTED] OM> cc: Sent by: MQSeries Subject: Re: Heartbeats and Disconnect interval List <[EMAIL PROTECTED] N.AC.AT> 11/12/2003 02:28 PM Please respond to MQSeries List Peter, This is what I think the quoted passage below is describing: The sender channel sends the heartbeat flow to the receiver. The receiver channel code, several versions ago, was blocking, and the receiver channel was blocked while waiting to have something sent to it by the sender. The introduction of heartbeats, which were not in the original product, allowed an operator on the receiver side of the channel to stop the channel and have the stop command take affect at the next heartbeat. Without heartbeats, the receiver was blocked, and the channel could not be stopped from the receiver end until either 1) the sender sent a message, or 2) the sender sent some data to inform the receiver that the disconnect interval had expired. -Tom ====================================================== Tom Schneider / IBM Global Services (513) 274-4034 [EMAIL PROTECTED] ====================================================== "Potkay, Peter M (PLC, IT)" <[EMAIL PROTECTED]> Sent by: MQSeries List <[EMAIL PROTECTED]> 11/12/2003 12:50 PM Please respond to MQSeries List To: [EMAIL PROTECTED] cc: Subject: Re: Heartbeats and Disconnect interval Sorry, there is now way I can read between the lines on the quote you have there. I would certainly take that quote to mean that a Heartbeat would disconnect a channel and put it inactive, which is not the way it works. The quote would be accurate if you just stuck the words "Lack of" in front of the whole thing. Typo in the manual??? -----Original Message----- From: Bill Anderson [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 12, 2003 12:33 PM To: [EMAIL PROTECTED] Subject: Re: Heartbeats and Disconnect interval Peter, The way you said it, is exactly the way I have always believed it to work. My confusion started when I was reading the intercommunication guide (counting sheep never has put me to sleep as well as the intercommunication guide!) and saw the following: Heartbeat flows unblock the receiving MCA, which is waiting for messages to arrive or for the disconnect interval to expire. When the receiving MCA is unblocked it can disconnect the channel without waiting for the disconnect interval to expire. Does IBM mean something other than going inactive when they say disconnect? Cheers Bill Anderson Senior Systems Analyst SITA Atlanta, GA 770-303-3503 (office) 404-915-3190 (cell) [EMAIL PROTECTED] http://www.mconnect.aero/ "Potkay, Peter M (PLC, IT)" To: [EMAIL PROTECTED] <[EMAIL PROTECTED] cc: RTFORD.COM> Subject: Re: Heartbeats and Disconnect interval Sent by: MQSeries List <[EMAIL PROTECTED] AC.AT> 11/12/2003 11:05 AM Please respond to MQSeries List Heartbeats flow back and forth when things are happy. As long as things are happy, the heartbeats just let each side know that the other side is alive and kicking during periods where no real MQ messages are flowing. Heartbeats will not cause a channel to go inactive. A lack of the responding heartbeat will. As long as the heartbeats flow, the channel stays up, until the DISCINT is reached, at which point the channel goes to inactive on both side. -----Original Message----- From: Bill Anderson [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 12, 2003 10:42 AM To: [EMAIL PROTECTED] Subject: Heartbeats and Disconnect interval I understand what heartbeat and disconnect intervals are and what they do, but one thing puzzles me. The heartbeat should be set significantly lower than the disconnect interval. And, the heartbeat will cause the receiver channel to go inactive in one of two ways: 1. when a heartbeat is sent, one of the things it does is "unblock" a receiver that is waiting for a message / disconnect interval to expire 2. When no heartbeat is sent when one is expected the receiver can go inactive. So my confusion is, if the above is accurate, the disconnect interval would never be the cause of a channel going inactive because the heartbeat would intervene at a much quicker rate. Once in awhile, ya think you understand something, then one day you say, hey, something aint right here! Thanks in advance Bill Anderson Senior Systems Analyst SITA Atlanta, GA 770-303-3503 (office) 404-915-3190 (cell) [EMAIL PROTECTED] http://www.mconnect.aero/ 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 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. 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 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 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
