| Author |
Message
|
| vishwanath_rs |
 Posted: Tue Nov 15, 2005 4:12 am Post subject: How to make the [b]channels up and Running all the Times[/b. |
 |
|
Newbie
Joined: 15 Nov 2005
Posts: 8
|
Dear Friends,
After a day of time my channels are becoming in-active. because of this Again I need to restart the channels every time frequently. so I think actually in Production environment it should not Happen. so please dear friends, guide me how to make the channels up and running all the times
I found one option like Dis-connect Interval, which will carry the default value of 6000. and this fiels takes maximum of 999999. By chance if it crosses 999999 seconds.. then the channels will become in-active. I think idealy it should not happen. so please suggest me how to make the Channels up and Running all the times throughout the years.
one more option is there like short retry count and long retry count.. which will help only for the retrying to connect to the remote que-manager after specified intervals of time.
so I am bit confused how to set the channels up and running all the times.
it would be great help, if anybody helps me to resolve this problem.
Thanks and Regards,
Vishwanath. |
|
| Back to top |
|
 |
| javagate |
| Posted: Tue Nov 15, 2005 4:14 am Post subject: |
|
|
Disciple
Joined: 15 Nov 2004
Posts: 159
|
On z/OS if you set the Dis-connect Interval to 0, they will stay active.
Did you set up a process to start the channels on the arrival of a message? 
_________________
WebSphere Application Server 7.0 z/OS &
MQ 6.0. I work with WebSphere in the real world not in some IBM lab. |
|
| Back to top |
|
|
| bower5932 |
| Posted: Tue Nov 15, 2005 4:58 am Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
| You might want to look at the Intercommunication manual. It gives details on the various states of channels and what to do to keep them in the 'right' states. |
|
| Back to top |
|
|
| meenakshi |
| Posted: Tue Nov 15, 2005 5:32 am Post subject: |
|
|
Novice
Joined: 15 Jun 2005
Posts: 11
Location: India
|
| Setting of the DISCINT attribute of the channel to 0 will not disconnect the channel. I would suggest trigger starting your channels when a message arrives on the transmission queue. This way you can avoid restatting of channels and also not keeping them active all the time. |
|
| Back to top |
|
|
| sandiksk |
| Posted: Tue Nov 15, 2005 6:49 am Post subject: |
|
|
Centurion
Joined: 08 Jun 2005
Posts: 133
|
settinga value of zero for the disconnect interval will keep the channels alive all the time, but it would overload ur network,( unless u have date going through all the time) so i would suggest implementing triggering and setting the disconnect value accordingly.
you definetely need to look into the manuals |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Tue Nov 15, 2005 5:48 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
Running channels without MQ messages flowing across them are not going to overload a network. At most, you will heartbeats flowing back and forth if you choose to use them, and they are something like 12 bytes each. I don't think that's going to overload a network.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| shsiow |
| Posted: Tue Nov 15, 2005 6:15 pm Post subject: |
|
|
Newbie
Joined: 01 Sep 2005
Posts: 7
|
Use triggering.
Take your sender channel name and put it in your transmission queue trigger data. Leave the process name blank and specific the trigger depth, so, whenever your transmisson queue depth reached/existed the trigger depth (1 perhaps), MQ itself will bring up the sender channel automatically, no network overload.  |
|
| Back to top |
|
|
| kevinf2349 |
| Posted: Tue Nov 15, 2005 8:31 pm Post subject: |
|
|
Grand Master
Joined: 28 Feb 2003
Posts: 1311
Location: USA
|
I don't suppose you used the search function to see the many many discussions on the this subject? 
Hopsla...is there a TT on this subject? 
...and just so we don't upset people and get accused of giving 'stock answers' .....
As others have stated triggering is an excellent method for starting channels when there are messages to be tranmitted, however it really depends on your business requirements. There are pros and cons to either method.
Using a DISCINT of zero will, as other have stated, keep the channel active and you can still trigger the channel so that you don't have to worry about startup scripts etc. Keeping a channel running will result in some overhead (polling etc) but, as Peter indicated, this will not 'overload a network' if it does, then your network was close to overload in the first place.
Now....the down side of keeping a channel up is that it is more prone to being effected by external network events. (firewall crashing, network brain-farts etc). Of course these can be recoverable but you need to code the channel defaults to make them so. Another down side (and this may or may not be a concern to your site) is if you use encryption. Encryption keys are negotiated at channel start...the longer the channel is running, then theorectically the more time a hacker has to break the encryption. Like I say, this may not be a big deal to you.
Now trigger channels with 'tuned' disconnect intervals are wonderful. All our channels here are triggered but they too have a down side. The downside is that if the channel is inactive the first message (the one causing the trigger message to get generated) will take longer to 'roundtrip' while MQ starts the queue manager. This is barely noticable in our shop but YMMV.
So...in conclusion...if your application demands response times in nano seconds...don't trigger the channels....and probably don't use MQ anyway  If you can stand one message taking slightly longer then I recommend trigger channels with 'good' disconnect intervals.
Hope this helps |
|
| Back to top |
|
|
| vishwanath_rs |
| Posted: Wed Nov 16, 2005 10:56 pm Post subject: Thanks Friends |
|
|
Newbie
Joined: 15 Nov 2005
Posts: 8
|
Thanks Dear Friends... 
I got very good Knowledge from the discussion you people made on this Topic..
Once Again Thanks a lot |
|
| Back to top |
|
|
|
|
