| Author |
Message
|
| ashu |
 Posted: Tue May 08, 2007 1:00 am Post subject: Channel Initiator not working... |
 |
|
Centurion
Joined: 11 Nov 2006
Posts: 132
|
Hello,
The steps that I have followed so far are as follows
(Distributed Queing artifacts are already in place...)
1) in XMITQ the INITQ=SYSTEM.CHANNEL.INITQ.
2) in XMITQ the TRIGDATA={channel name}
3) listener started on receiving end.
4) runmqchi called with qmgr(sending) and initq(SYSTEM.CHANNEL.INITQ) options provided.
** I also read somewhere that the channel initiator is automatically started when the QMGR is started so tried without running runmqchi too...
But still when i put a message on the remote queue the message is stuck on the XMITQ.However when the channel is explicitly started the message is received by the LQ on receiving QMGR.
WHich tells me that the Channel Initiator(CI) is not able to start the channel for me...
If i have read correctly the CI gets the name of the channel to be started from the TRIGDATA field of the trigger message as set in XMITQ definition.
Sorry for so much text...but I wanted to be very clear....
Can some one guide? 
Regards,
_________________
Ashu
"It is simple to be Happy but difficult to be Simple" |
|
| Back to top |
|
 |
| Vitor |
| Posted: Tue May 08, 2007 1:22 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
|
| Back to top |
|
|
| ashu |
| Posted: Tue May 08, 2007 1:34 am Post subject: |
|
|
Centurion
Joined: 11 Nov 2006
Posts: 132
|
I'm on 5.3
_________________
Ashu
"It is simple to be Happy but difficult to be Simple" |
|
| Back to top |
|
|
| Nigelg |
| Posted: Tue May 08, 2007 2:50 am Post subject: |
|
|
Grand Master
Joined: 02 Aug 2004
Posts: 1046
|
Try setting the TRIGGER attribute of the xmitq
_________________
MQSeries.net helps those who help themselves.. |
|
| Back to top |
|
|
| ashu |
| Posted: Tue May 08, 2007 3:03 am Post subject: |
|
|
Centurion
Joined: 11 Nov 2006
Posts: 132
|
| Nigelg wrote: |
| Try setting the TRIGGER attribute of the xmitq |
I have already done that multiple times....I know it gets set to NOTRIGGER...so I have alwys kept watch on it...
_________________
Ashu
"It is simple to be Happy but difficult to be Simple" |
|
| Back to top |
|
|
| ashu |
| Posted: Tue May 08, 2007 5:11 am Post subject: |
|
|
Centurion
Joined: 11 Nov 2006
Posts: 132
|
I have suddenly realized that the QMGR is not putting a trigger message in the INITQ.
to verify this I actually set a trigger on the SYSTEM.CHANNEL.INITQ ...which runs a simple process such as NOTEPAD.
Actually what I was trying to figure out was whether there was a problem with the QMGR of the Channel Initiator...
The SYSTEM.CHANNEL.INITQ would be empty if,
1) QMGR did not put a trigger message on it.
2) Channel Initiator read the message from it.
if the first case were to be false...then the trigger set on SYSTEM.CHANNEL.INITQ should fire...which is not happening...hence the conclusion....
Why has the QMGR suddenly lost the ability to put trigger messages...
both the XMITQ and SYSTEM.CHANNEL.INITQ have TRIGGER attribute set...
Regards,
_________________
Ashu
"It is simple to be Happy but difficult to be Simple" |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue May 08, 2007 5:18 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| ashu wrote: |
to verify this I actually set a trigger on the SYSTEM.CHANNEL.INITQ ...which runs a simple process such as NOTEPAD.
|
Don't do this. Run the monitor as a foreground process and look to see if the message goes past.
Remember the INITQ must be open for a trigger message to be generated (condition eight).
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| ashu |
| Posted: Tue May 08, 2007 5:20 am Post subject: |
|
|
Centurion
Joined: 11 Nov 2006
Posts: 132
|
| Quote: |
| Run the monitor as a foreground process and look to see if the message goes past. |
I'm not aware of how this is done ....! 
_________________
Ashu
"It is simple to be Happy but difficult to be Simple" |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue May 08, 2007 5:22 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| ashu wrote: |
| Quote: |
| Run the monitor as a foreground process and look to see if the message goes past. |
I'm not aware of how this is done ....! |
Start a command prompt and run it from the command line. It's in the System Admin manual. You'll see the message as it's echoed to sysout.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue May 08, 2007 5:26 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
No, this is channel initiation, not program initiation.
Don't run anything in the foreground.
Setting a trigger on initq isn't going to tell you anything. If the CHINIT is running, then the initq will always be open for input, so there will never be a trigger generated!
The XMITQ trigger should not be getting trigger disabled, unless you're attempting to trigger it on DEPTH rather than FIRST.
And you shouldn't be trying to trigger a CHANNEL on depth! Or if so, you shouldn't be using the normal CHINIT.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| ashu |
| Posted: Tue May 08, 2007 5:26 am Post subject: |
|
|
Centurion
Joined: 11 Nov 2006
Posts: 132
|
I'll check out the System Admin manual...
_________________
Ashu
"It is simple to be Happy but difficult to be Simple" |
|
| Back to top |
|
|
| ashu |
| Posted: Tue May 08, 2007 5:32 am Post subject: |
|
|
Centurion
Joined: 11 Nov 2006
Posts: 132
|
| jefflowrey wrote: |
No, this is channel initiation, not program initiation.
Don't run anything in the foreground.
Setting a trigger on initq isn't going to tell you anything. If the CHINIT is running, then the initq will always be open for input, so there will never be a trigger generated!
The XMITQ trigger should not be getting trigger disabled, unless you're attempting to trigger it on DEPTH rather than FIRST.
And you shouldn't be trying to trigger a CHANNEL on depth! Or if so, you shouldn't be using the normal CHINIT. |
I have the trigtype=FIRST in the XMITQ and trigdepth=1 as given in all the literatures that I read for Channel Initiation...
_________________
Ashu
"It is simple to be Happy but difficult to be Simple" |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue May 08, 2007 5:34 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Okay.
So, let's start with the basics. Instead of worrying about whether or not a trigger message is being produced, let's make sure we know what the real problem is.
What state is the channel in?
What version of the product are you on?
What OS?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| ashu |
| Posted: Tue May 08, 2007 5:39 am Post subject: |
|
|
Centurion
Joined: 11 Nov 2006
Posts: 132
|
@Jeff,
I'm using v5.3 on WindowsNT .
The channel state is :STOPPED
_________________
Ashu
"It is simple to be Happy but difficult to be Simple" |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue May 08, 2007 5:44 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
STOPPED channels never start on their own.
You must START them manually.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
|
|
