My understanding of how Heartbeats work is the same as stated in the manual.
The heartbeat kicks in when there are NO messages on the transmission queue.
If you set it to 30 sec, the first heartbeat would flow 30 sec AFTER the
LAST message leaves the transmission queue (leaving the xmit queue empty).
This tells the other side (receiver) to close itself and release the
resources WITHOUT waiting for the diconnect interval to kick in. And as a
result, the channel ends at that point...

Ruzi

-----Original Message-----
From: Bill Anderson [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 12, 2003 1:34 PM
To: [EMAIL PROTECTED]
Subject: Re: Heartbeats and Disconnect interval


I find it hard to believe IBM would write a technical document that was
difficult to Interpret (NOT)

All kidding aside, I am going with the typo theory for now. I just let the
manual rattle my confidence a little I guess

Hey IBM! what up?

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 12:50 PM
                      Please respond to
                      MQSeries List






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


This email communication is intended as a private communication for the sole
use of the primary addressee and those individuals listed for copies in the
original message. The information contained in this email is private and
confidential and if you are not an intended recipient you are hereby
notified that copying, forwarding or other dissemination or distribution of
this communication by any means is prohibited.  If you are not specifically
authorized to receive this email and if you believe that you received it in
error please notify the original sender immediately.  We honour similar
requests relating to the privacy of email communications.

Cette communication par courrier ilectronique est une communication privie `
l'usage exclusif du destinataire principal ainsi que des personnes dont les
noms figurent en copie.  Les renseignements contenus dans ce courriel sont
confidentiels et si vous n'jtes pas le destinataire privu, vous jtes avisi,
par les prisentes que toute reproduction, tout transfert ou toute autre
forme de diffusion de cette communication par quelque moyen que ce soit est
interdit.  Si vous n'jtes pas spicifiquement autorisi ` recevoir ce courriel
ou si vous croyez l'avoir regu par erreur, veuillez en aviser l'expiditeur
original immidiatement.  Nous respectons les demandes similaires qui
touchent la confidentialiti des communications par courrier ilectronique.

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

Reply via email to