| Author |
Message
|
| kirk_daledovich |
 Posted: Wed Jan 21, 2004 12:56 pm Post subject: A triggered local queue issue. |
 |
|
Newbie
Joined: 21 Jan 2004
Posts: 3
|
I currently have a application that sends messages to a remote queue on a Window based MQ manager which in turns sends it up to a local queue on an OS390 MQ manager. Then the local queue on the mainframe triggers a process.(this works correctly)
I was to trying to eliminate a hop by going from the application straight to the MQ manager on the OS390 system. But when I do this the messages stack up on the local queue on the OS390 system and is not triggering the process.(this does not work at all)
We are on V5.3 on the window side and OS390.
Thanks for any help on this issue. |
|
| Back to top |
|
 |
| mrlinux |
| Posted: Wed Jan 21, 2004 1:22 pm Post subject: |
|
|
Grand Master
Joined: 14 Feb 2002
Posts: 1261
Location: Detroit,MI USA
|
Are you connecting to the Mainframe via Server/Client connection.
And if it is server are the channels convert option the same as the one that works ???
_________________
Jeff
IBM Certified Developer MQSeries
IBM Certified Specialist MQSeries
IBM Certified Solutions Expert MQSeries |
|
| Back to top |
|
|
| kirk_daledovich |
| Posted: Wed Jan 21, 2004 1:35 pm Post subject: |
|
|
Newbie
Joined: 21 Jan 2004
Posts: 3
|
The application is using an MQ client on the server.
I have the MQSERVER enviroment varible setup to point to the MQ manager via TCP.
Currently the MQ client talks to the MQ manager on the windows server then is sent up from that MQ manager to the MQ manager on the OS390 system via channels. |
|
| Back to top |
|
|
| mqonnet |
| Posted: Wed Jan 21, 2004 1:46 pm Post subject: |
|
|
Grand Master
Joined: 18 Feb 2002
Posts: 1114
Location: Boston, Ma, Usa.
|
Make sure that your queue is set for triggering and that all the conditions to trigger a process are met. Because it doesnt really make any difference if the message that is put to this local queue on Os/390 is by a local app or by the MCA(as is in your case where it is working OK). There must be some difference in the way you set up everything for triggering.
So, check the following.
1) Is your trigger monitor running.
2) Is the queue set to TRIGGER.
3) Has the trigger monitor opened the same initiation queue that is referred by the local queue on Os/390.
4) Is the process def appropriate.
Refer the the manuals for all the trigger conditions other than what i posted. These are the ones that are usually missed out.
Hope this helps.
Cheers
Kumar |
|
| Back to top |
|
|
| kirk_daledovich |
| Posted: Wed Jan 21, 2004 2:39 pm Post subject: |
|
|
Newbie
Joined: 21 Jan 2004
Posts: 3
|
Nothing has changed on the OS390 mq manager where the triggered queue is.
The only diffence is that the PUT from the server is going directly to the LOCAL triggered queue, instead of going to a remote queue then the remote queue sending it to the local triggered queue.
Is thier an option on the put that would disallow a triggered queue not to trigger? |
|
| Back to top |
|
|
| EddieA |
| Posted: Wed Jan 21, 2004 5:34 pm Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
Ah ha. When the client is connected, the Queue is open. So, MQ will NOT generate a trigger. However, when the client disconnects, then MQ should fire off the trigger.
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Thu Jan 22, 2004 1:04 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
You obviously must open the queue to put the message. Just make sure you open for OUTPUT only. I bet you your client is specifying (needlessly) the INPUT option on the OPEN, which is interfering with the triggering. If you don't use the input option, the client app will not effect triggering, even if it has the queue open.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
|
|
