| Author |
Message
|
| froldan |
 Posted: Sat Jul 27, 2002 3:40 pm Post subject: Channels always Running |
 |
|
Novice
Joined: 17 Jul 2002
Posts: 15
|
Hey everybody, I know that the channels can be started
with a trigger (based on demand messaging), but my boss want to have the channels
always running, can i do this and how?
Thanks in advance
Regards |
|
| Back to top |
|
 |
| PeterPotkay |
| Posted: Sun Jul 28, 2002 5:28 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
You want to lool at the disconnect interval (DISCINT) attribute for the channels.
From the Intercommunication Hnadbook...
This is a time-out attribute, specified in seconds, for the server, cluster-sender, sender, and cluster-receiver channels. The interval is measured from the point at which a batch ends, that is when the batch size is reached or when the batch interval expires and the transmission queue becomes empty. If no messages arrive on the transmission queue during the specified time interval, the channel closes down. (The time is approximate.)
On all platforms except OS/390 with CICS, you can specify any number of seconds from zero through 999 999 where a value of zero means no disconnect; wait indefinitely.
In OS/390 using CICS, you can specify any number of seconds from zero through 9999 where a value of zero means disconnect as soon as the transmission queue is empty.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| bigdavem |
| Posted: Sun Jul 28, 2002 10:26 pm Post subject: |
|
|
Acolyte
Joined: 16 Sep 2001
Posts: 69
Location: Sydney, Australia
|
I'm not sure why your boss would care if the channel is running all the time?
Be careful - if you don't have an initiator and the channel drops out for some reason it won't restart without manual intervention (or a rule executed by a monitoring tool). I'd tend to go with an initiator and a reasonable disconnect interval ("reasonable" would depend on the frequency of messages across that channel). |
|
| Back to top |
|
|
| mrlinux |
| Posted: Mon Jul 29, 2002 4:50 am Post subject: |
|
|
Grand Master
Joined: 14 Feb 2002
Posts: 1261
Location: Detroit,MI USA
|
If you set the disconnect interval to zero it will never timeout and disconnect, The other reasons for disconnect are remote system restart's or network failures has long as you bump up the short retries to exceed those times the channel will recover on it's own for the most part.
Sometimes the errors will leave channels in-doubt and if that happens wether you have a disconnect interval or not, you will need to provide
some intervention to recover.
_________________
Jeff
IBM Certified Developer MQSeries
IBM Certified Specialist MQSeries
IBM Certified Solutions Expert MQSeries |
|
| Back to top |
|
|
| arinduer |
| Posted: Mon Jul 29, 2002 4:54 am Post subject: |
|
|
Acolyte
Joined: 13 Aug 2001
Posts: 50
Location: Phuket, Thailand
|
Hmmm. Yeah, maybe you should explain to your boss that the channels do not necessarily have to run 24x7. In our large organization, channels trigger when a message hits the xmit queue. Then it times out after a default time of inactivity, and get turned back on again as soon as another message hits the xmit queue--trigdata set to channel name and TRIGTYPE(FIRST). If you look at /var/mqm/qmgrs/QMGRNAME/errors/AMQERR01.LOG you would be able to see when the channels start and stop... Also, another trick that we use when looking at channels is entering the command: "dis chs(*) lstmsgti" . This is cool because it lists all the channels and their status, and also the time the last message was sent. We also use BMC Patrol and can view the status of all the channels (type, inactive/running, their current sequence number, messages, bytes, xmit depth, and even the connection names (CONNAME) parameter).  |
|
| Back to top |
|
|
| froldan |
| Posted: Mon Jul 29, 2002 7:12 am Post subject: |
|
|
Novice
Joined: 17 Jul 2002
Posts: 15
|
Great folks, thanks for all your answers.
i think i will explain the vantages of triggering the channels
instead of run the channels always.
Other question , how can i catch the event when a channel gets stopped ?
Thanks |
|
| Back to top |
|
|
| mrlinux |
| Posted: Mon Jul 29, 2002 7:31 am Post subject: |
|
|
Grand Master
Joined: 14 Feb 2002
Posts: 1261
Location: Detroit,MI USA
|
you can purchase software that monitors event queues or you can write your own (Examples are on IBM Website)
http://www-4.ibm.com/software/ts/mqseries/txppacs/txpsumm.html
I have worked in places where both have been done, channels always active and others that have timeouts.
One last consideration is the channel startup time will slow down the
transaction that follows after the disconnect. This is problay less than 1
second but it needs to be considered for Request/Response times.
_________________
Jeff
IBM Certified Developer MQSeries
IBM Certified Specialist MQSeries
IBM Certified Solutions Expert MQSeries |
|
| Back to top |
|
|
| froldan |
| Posted: Mon Jul 29, 2002 7:38 am Post subject: |
|
|
Novice
Joined: 17 Jul 2002
Posts: 15
|
Excellent Consideration Master Yoda !
I am doing transactions from ATM's, and the time response is very important, even one second matters (Plus my application time response and the time of data traveling across the network).
Thanks |
|
| Back to top |
|
|
|
|
