| Author |
Message
|
| lpizzi |
 Posted: Wed Mar 06, 2002 12:15 am Post subject: |
 |
|
Newbie
Joined: 15 Jan 2002
Posts: 4
Location: Italia
|
Hy.I'm italian and my english is bad but i hope you understand my problem.
I work on unix system (sun aix digital siemens) that dialog whit mvs/cics machine.
The sender unix.to.host when starting, work correctly, but when there isen't traffic for a period it go in inactive mode. This is certanely normal but the channel not start automatically where a new message arrive. This is for all machine unix like.
There is a method or a sample program for resolve it ??
Thank for all |
|
| Back to top |
|
 |
| dgolding |
| Posted: Wed Mar 06, 2002 1:21 am Post subject: |
|
|
Yatiri
Joined: 16 May 2001
Posts: 668
Location: Switzerland
|
Ciao Ipizzi
You need to trigger the transmit queue:
runmqsc
ALTER QL(<Name of transmit queue>) +
TRIGDATA(<Name of Channel to start>) +
INITQ(SYSTEM.CHANNEL.INITQ) +
TRIGGER(YES) # or maybe TRIGGER(ENABLE), I always forget!
Your channel initiator should be running, ps -ef¦grep runmqchi should tell you.
|
|
| Back to top |
|
|
| EddieA |
| Posted: Wed Mar 06, 2002 12:45 pm Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
It's neither. It's just TRIGGER.
You might also want to use TRIGTYPE(FIRST). I know it's the default, but this way you know EXACTLY what it is.
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
| muralidhar |
| Posted: Wed Mar 06, 2002 4:30 pm Post subject: |
|
|
Acolyte
Joined: 28 Feb 2002
Posts: 50
|
| If you like your sender channel running all the time, you can set its disconnect interval to '0'. |
|
| Back to top |
|
|
| lpizzi |
| Posted: Thu Mar 07, 2002 12:10 am Post subject: |
|
|
Newbie
Joined: 15 Jan 2002
Posts: 4
Location: Italia
|
Seem to work.....
Thank at all. |
|
| Back to top |
|
|
| kspranava |
| Posted: Thu Apr 08, 2004 2:18 am Post subject: same problem |
|
|
Centurion
Joined: 27 Apr 2003
Posts: 124
|
Hi,
Even am facing the same probem except for one thing, once the sender channels enters inactive mode, TRIGGER option in Transmit Queue is set to "OFF" automatically and msgs get struck in transmit q itself . This appears strange to me. Can anybody explain why it is so? also how to overcome this problem?
Sometimes I found, when the receiver channel is restarted while sender is either in running or inactive mode, TRIGGER option of transmit queue is set to "OFF". But am not sure this scenario is reated to this problem 
-Pranava |
|
| Back to top |
|
|
| devin |
| Posted: Mon Apr 12, 2004 9:38 am Post subject: |
|
|
Voyager
Joined: 27 Oct 2003
Posts: 82
|
hi,
We have the channel disconnect interval set to 0 .
And we are not using triggering.
THe sender channel is INACTIVE state after a reboot and queue manager restarts.
We have to start the channel for it to go into retrying or running states depending on the network connection.
Is this correct behavior?
I am assuming the sender channel should be started automatically.
I have checked the SYSTEM.CHANNEL.SYNCQ and there are no more than 3 messages.
The channel initiator is running.
It would be great if anybody could throw some light on this.
Thanks
_________________
IBM Certified Solution Designer -
WebSphere MQ Workflow 3.4 |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Mon Apr 12, 2004 1:53 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
The behaviour you are seeing is normal.
If you want the channels to start automatically if there are messages in the transmit queue, turn triggering on, regardless of what your DISCINT is.
DISCINT 0 means your channels are up forever, meaning they are more likely to run into problems due to networks issues. Don't use 0 unless you have a valid reason to. The only one I can think of is you can't wait the second or so to have a channel startup via triggerring.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
|
|
