| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| MQSeries Client Channels and KAINT (w/KeepAlive=Yes) |
« View previous topic :: View next topic » |
| Author |
Message
|
| WannaBeInAParker |
 Posted: Wed Nov 03, 2004 8:08 am Post subject: MQSeries Client Channels and KAINT (w/KeepAlive=Yes) |
 |
|
Voyager
Joined: 09 Dec 2003
Posts: 81
|
We are working on enabling KeepALive at the MQSeries level for our queue managers. The documentation states that KAINT will be used as the interval on a channel by channel basis. The KAINT doc states that the KAINT function only works on MVS as show below (Note the last line):
KeepAlive Interval (KAINT)
The KeepAlive Interval parameter is used to specify a time-out value for a channel.
The KeepAlive Interval parameter is a value passed to the communications stack
specifying the KeepAlive timing for the channel. It allows you to specify a different
keepalive value for each channel.
The value indicates a time, in seconds, and must be in the range 0 to 99999. A
KeepAlive value of 0 indicates that channel KeepAlive is not enabled for the
channel. When the KeepAlive Interval is set to 0, keepalive still occurs if a value
has been specified for TCP/IP keepalive. On z/OS, this occurs when the
TCPKEEP=YES parameter is specified in CSQ6CHIP. On other platforms, it occurs
when the KEEPALIVE=YES parameter is specified in the TCP stanza in the
distributed queuing configuration file.
You can also set KAINT to a value of AUTO. If KAINT is set to AUTO, the
keepalive value is based on the value of the negotiated HBINT as follows:
Table 8. Negotiated HBINT value and the corresponding KAINT value
Negotiated HBINT KAINT
>0 Negotiated HBINT + 60 seconds
0 0
This parameter is valid for all channel types. The value is ignored for all channels
that have a TransportType (TRPTYPE) other than TCP or SPX
KAINT is only available on WebSphere MQ for z/OS.
Can anyone prove/disprove this?
Thanks in advance
WannaBe |
|
| Back to top |
|
 |
| Nigelg |
| Posted: Wed Nov 03, 2004 8:23 am Post subject: |
|
|
Grand Master
Joined: 02 Aug 2004
Posts: 1046
|
You just need to believe the manual!
Try it. Set KAINT on a channel on a distributed qmgr, and see what happens - nothing. |
|
| Back to top |
|
|
| WannaBeInAParker |
| Posted: Wed Nov 03, 2004 8:34 am Post subject: |
|
|
Voyager
Joined: 09 Dec 2003
Posts: 81
|
Nigelg,
Thanks. I just can't get myself to believe the manual! The reason why is that why would the option be included on the channel definition? Also, it is almost like an afterthought in the doc, like "oh by the way...".
So basically the TCP keep Alive at the OS level is the interval on the open systems.
-WannaBe- |
|
| Back to top |
|
|
| CMX |
| Posted: Fri Nov 05, 2004 4:58 pm Post subject: Re: MQSeries Client Channels and KAINT (w/KeepAlive=Yes) |
|
|
Newbie
Joined: 05 Nov 2004
Posts: 4
|
So is there a difference between setting the KeepAlive in the MQSC and the TCP Stanza??
Also, for Windows, Unix and other systems, would it be better to use KeepAlive on TCP Stanza or should we just use HBINT as an alternatives??
Please advise 
| WannaBeInAParker wrote: |
We are working on enabling KeepALive at the MQSeries level for our queue managers. The documentation states that KAINT will be used as the interval on a channel by channel basis. The KAINT doc states that the KAINT function only works on MVS as show below (Note the last line):
KeepAlive Interval (KAINT)
The KeepAlive Interval parameter is used to specify a time-out value for a channel.
The KeepAlive Interval parameter is a value passed to the communications stack
specifying the KeepAlive timing for the channel. It allows you to specify a different
keepalive value for each channel.
The value indicates a time, in seconds, and must be in the range 0 to 99999. A
KeepAlive value of 0 indicates that channel KeepAlive is not enabled for the
channel. When the KeepAlive Interval is set to 0, keepalive still occurs if a value
has been specified for TCP/IP keepalive. On z/OS, this occurs when the
TCPKEEP=YES parameter is specified in CSQ6CHIP. On other platforms, it occurs
when the KEEPALIVE=YES parameter is specified in the TCP stanza in the
distributed queuing configuration file.
You can also set KAINT to a value of AUTO. If KAINT is set to AUTO, the
keepalive value is based on the value of the negotiated HBINT as follows:
Table 8. Negotiated HBINT value and the corresponding KAINT value
Negotiated HBINT KAINT
>0 Negotiated HBINT + 60 seconds
0 0
This parameter is valid for all channel types. The value is ignored for all channels
that have a TransportType (TRPTYPE) other than TCP or SPX
KAINT is only available on WebSphere MQ for z/OS.
Can anyone prove/disprove this?
Thanks in advance
WannaBe |
|
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
