Author |
Message
|
Djeyli |
Posted: Thu Apr 25, 2002 3:25 am Post subject: |
|
|
 Apprentice
Joined: 03 Apr 2002 Posts: 28 Location: New Zealand
|
How is it possible to force the Channel to start automatically when you launch MQ ? And is it possible to make it so that it is always active ? I am using MQseries 5.2.1 on a Win2k machine. Thanks. |
|
Back to top |
|
 |
mrlinux |
Posted: Thu Apr 25, 2002 4:32 am Post subject: |
|
|
 Grand Master
Joined: 14 Feb 2002 Posts: 1261 Location: Detroit,MI USA
|
Setup triggering on the transmit queue for the channel definition
Must have Channel Initiator started
under the trigger tab
Trigger Control ON
Trigger Type First
Trigger Data CHANNEL_NAME
INITIATION QUEUE SYSTEM.CHANNEL.INITQ
Always active, Channel Definition Disconnect
interval must be set to 0 to disable timeouts
_________________
Jeff
IBM Certified Developer MQSeries
IBM Certified Specialist MQSeries
IBM Certified Solutions Expert MQSeries
[ This Message was edited by: mrlinux on 2002-04-25 05:33 ] |
|
Back to top |
|
 |
vmcgloin |
Posted: Thu Apr 25, 2002 4:41 am Post subject: |
|
|
Knight
Joined: 04 Apr 2002 Posts: 560 Location: Scotland
|
Triggering on the transmit queue will only start the channel when a message is on the transmission queue. You still might encounter for example an application timeout while it starts.
Under NT you can define a new channel which will start automatically when MQ is started using the MQSeries Services GUI. I assume the same is true of W2K.
As for making it always active, set the disconnect interval (DISCINT) on the channel to 0. A value of zero means no disconnect; wait indefinitely.
Vicky
|
|
Back to top |
|
 |
mrlinux |
Posted: Thu Apr 25, 2002 4:54 am Post subject: |
|
|
 Grand Master
Joined: 14 Feb 2002 Posts: 1261 Location: Detroit,MI USA
|
There is no way under the MQSeries Services to start a channel(short of a custom service which you would have to write script/bat), Only the Listener/Initiator, you need to have the transmit Queue set up for triggering+have the initiator set to start automaticly.
_________________
Jeff
IBM Certified Developer MQSeries
IBM Certified Specialist MQSeries
IBM Certified Solutions Expert MQSeries
[ This Message was edited by: mrlinux on 2002-04-25 05:56 ] |
|
Back to top |
|
 |
vmcgloin |
Posted: Thu Apr 25, 2002 5:42 am Post subject: |
|
|
Knight
Joined: 04 Apr 2002 Posts: 560 Location: Scotland
|
Hi,
I'm not trying to pick a fight but, looking at MQ 5.2.1 on NT, I can define a channel service. This just refers to the runmqchl command, and provides automatic startup & recovery. You need to already have the sender/receiver channels defined in the usual way.
This looks like something new and fom playing around with it just now it may not be totally up to scratch. The traffic lights seem to have a problem keeping up with the status as shown by MQExplorer/runmqsc/taskmgr. Also, the service seems to take longer than its wait time before restarting after I killed the runmqchl process.
But, it does start the channel when I restart the qmgr without messages on the xmitq.
Can anyone who is actively using the channel service in 5.2.1 shed light on this?
Cheers,
Vicky
P.s. I would go with Jeff suggestion anyway since it is more portable to other platforms.
|
|
Back to top |
|
 |
mrlinux |
Posted: Fri Apr 26, 2002 3:51 am Post subject: |
|
|
 Grand Master
Joined: 14 Feb 2002 Posts: 1261 Location: Detroit,MI USA
|
Iam not intrested in having fights/flame wars. It appears that does work.
Well I prefer the channel trigger method for several reason, one as stated prevoisly it more portable across platforms, The other reason is more related
to disaster recovery, We backup all our QMGR Definitions so if the Queue Manager gets messed up from a crash (hasnt happened in a long long time)
instead of trying to figure out what is exactly wrong it is easier to delete
and recreate the queue manager from the definitions, I dont know if the services stuff would be easy to recreate.
NOTE: Deleting the QMGR and recreating is the fastest recovery sometimes, assuming you dont mind losing data (most of our messages are non persistant so we loose them after crash anyway)
_________________ Jeff
IBM Certified Developer MQSeries
IBM Certified Specialist MQSeries
IBM Certified Solutions Expert MQSeries |
|
Back to top |
|
 |
|