Thanks Paul. Very clear now.
Peter Potkay IBM MQSeries Certified Specialist, Developer [EMAIL PROTECTED] X 77906 -----Original Message----- From: Paul Clarke [mailto:[EMAIL PROTECTED]] Sent: Monday, December 02, 2002 3:11 PM To: [EMAIL PROTECTED] Subject: Re: Keep Alive vs Heartbeat - What's the diff? >Paul, >Keep Alive is configured at the machine level, correct? So all TCP >applications on a machine have to agree to a common value? Most platforms allow you to only set a machine wide keep alive interval, zOS is an exception, there may be others. Each socket application can merely choose to switch keepalive on or off. >You said HB doesn't apply on SVRCONN channels, but the below paragraph from >the Intercommunication handbook says it does? No I didn't. I said a SVRCONN channel can not heartbeat to a client *between* MQI calls. ><Quote> >This attribute is valid for sender, cluster-sender, server, receiver, >cluster-receiver, and requester channels. Other than on OS/390 and OS/400, >it also applies to server-connection and client-connection channels. On >these channels, heartbeats flow when a server MCA has issued an MQGET >command with the WAIT option on behalf of a client application. ><End Quote> Thanks for the book quote but there's a fair chance I wrote this. >So for Blocking Gets, the HB comes into play, but for all other times that >an MQClient might be connected, the Keep Alive pulse is what will catch the >MQClient dissappearing without disconnecting? Yes. >The manual says if 2 sides of a channel have different values, the larger is >used. Unless one side is ZERO, which means no HB? In that case ZERO trumps >the other side? Yes, if you like ZERO is treated as an infinite heartbeat value. Cheers, P. Paul G Clarke WebSphere MQ Development IBM Rochester,MN 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
