| Author |
Message
|
| kevin_22 |
 Posted: Tue Nov 29, 2005 2:01 am Post subject: QM-QM communicaton |
 |
|
Centurion
Joined: 08 Mar 2005
Posts: 100
|
Hai all,
I am trying for an automatic channel communication between two QM(QM2&QM3).
I created transmission queue with
Triggering -ON
Trigger Type-Every
trigger depth-1
trigger data -qm3(name of my sender channel on QM2)
initiation queue name: SYSTEM.CHANNEL.INITQ
sender channel is in inactive state.
When i kept the message in the remote queue by rfhuntil message is reaching the destination(q1 on QM3) but the channel are not comming to the inactive state. I assume they should be come to inactive state.
when i went into the forums and checked i found that i need to use "start chlinit" . i even tried for that and an error is comming with "AMQ9509: Program cannot open queue manager object."
and in application log with.....
" Program cannot open queue manager object.
The attempt to open either the queue or queue manager object 'SYSTEM.CHANNEL.INITQ' on queue manager 'QM2' failed with reason code 2042.
Ensure that the queue is available and retry the operation. "
Channel Initiater is running in QM2
is this different from "start chl"
Operating system: Windows 2000
MQ Version :5.3
plz... guide me.
Thanks,
kevin  |
|
| Back to top |
|
 |
| fschofer |
| Posted: Tue Nov 29, 2005 2:53 am Post subject: |
|
|
Knight
Joined: 02 Jul 2001
Posts: 524
Location: Mainz, Germany
|
Hi,
how is the DISCINT parameter of your sender channel configured ?
| Quote: |
DISCINT(integer)
The minimum time in seconds for which the channel waits for a message to arrive on the transmission queue, after a batch ends, before terminating the channel. A value of zero causes the message channel agent to wait indefinitely.
The value must be in the range zero through 999 999.
This parameter is valid only for channels with a channel type (CHLTYPE) of SVRCONN (on z/OS only), SDR, SVR, CLUSSDR, CLUSRCVR. |
Greetings
Frank |
|
| Back to top |
|
|
| wschutz |
| Posted: Tue Nov 29, 2005 3:17 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
And I'd use TRIGTYPE=FIRST (not every)...
_________________
-wayne |
|
| Back to top |
|
|
| kevin_22 |
| Posted: Tue Nov 29, 2005 4:06 am Post subject: |
|
|
Centurion
Joined: 08 Mar 2005
Posts: 100
|
Thanks for your response.... 
Yes it was with the sender channel DISCINT(x--inter)property. I tought x is represented in millisec. By default it is 6000. When i kept it to 2 , the channels are comming to inactive state.
But got some more issues in this like..
while i am using "start chinit " it is showing
35 : start chinit
AMQ9509: Program cannot open queue manager object.
why is this happening.... |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Nov 29, 2005 4:16 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
You probably don't need to start a channel initiator on Windows.
It usually runs automatically, unless you have done funny things when you created your QM.
What does the Services MMC show for your queue manager?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| kevin_22 |
| Posted: Tue Nov 29, 2005 4:34 am Post subject: |
|
|
Centurion
Joined: 08 Mar 2005
Posts: 100
|
In the services the channel initiator is running......
Is the channel initiator in the MQ Service is different from the "start chinit" ???
I stopped my channel initiator and executed "start chinit" and it worked this time but the "channel initiator" in the MQServices is still showing "stopped" status and while i am putting a message in the remote queue it is working asusual activating the channel. I have tried many time of refreshing the window but it still showing "stopped" status.
I am very thankful for u for guiding me in this issue....
kevin... |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Nov 29, 2005 4:47 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Just stop your qmgr entirely, and then start it again - using Explorer.
Don't bother with "start chinit". (this, by the way, stands for "start channel initiator"), at all.
There are known incompatibilities between the command line and the MMC based control methods for MQ 5.3 on Windows. If you really want to play around with stopping and starting the chinit from the command line, you can look at the command amqmdain.
It sounds like, other than the chinit, you have this working now?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
|
|
