| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| ALTER QL TRIGGER successful, but DIS QL TRIGGER still NOTRIG |
« View previous topic :: View next topic » |
| Author |
Message
|
| zhanghz |
 Posted: Fri Mar 06, 2009 2:06 am Post subject: ALTER QL TRIGGER successful, but DIS QL TRIGGER still NOTRIG |
 |
|
Disciple
Joined: 17 Jun 2008
Posts: 186
|
A queue is NOTRIGGER. Tried ALTER it to TRIGGER. There are messages inside the queue while doing the alter. ALTER showed successful, but DIS QL TRIGGER shows NOTRIGGER.
What might be the reason? And how to change it to TRIGGER?
It's a queue in message broker.
This is on z/OS. But I thought this might not limited to just z/OS, so I posted it here. |
|
| Back to top |
|
 |
| Vitor |
| Posted: Fri Mar 06, 2009 2:19 am Post subject: Re: ALTER QL TRIGGER successful, but DIS QL TRIGGER still NO |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| zhanghz wrote: |
A queue is NOTRIGGER. Tried ALTER it to TRIGGER. There are messages inside the queue while doing the alter. ALTER showed successful, but DIS QL TRIGGER shows NOTRIGGER.
|
Normal or transmit queue?
What kind of trigger?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Mar 06, 2009 2:21 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| What do you mean, "it's a queue in message broker"? |
|
| Back to top |
|
|
| kevinf2349 |
| Posted: Fri Mar 06, 2009 5:55 am Post subject: |
|
|
Grand Master
Joined: 28 Feb 2003
Posts: 1311
Location: USA
|
| What is the trigger type? DEPTH by any chance? |
|
| Back to top |
|
|
| zhanghz |
| Posted: Fri Mar 06, 2009 8:05 am Post subject: |
|
|
Disciple
Joined: 17 Jun 2008
Posts: 186
|
To Vitor and kevin: it's a normal local queue. Trigger type FIRST.
to jeff: It's a queue defined in a qmgr that is used by a MB, which WBIFN is conencted to. I thought to give as much information as possible, didn't mean to cause any confusion.
to all:
This was resolved. Application team changed something, then I was able to set TRIGGER on. As I was hurrying to leave office, I didn't wait to ask for details on what was changed. Will get some information on Monday. Thought someone might have encountered this, thus the post.. |
|
| Back to top |
|
|
| zhanghz |
| Posted: Tue Mar 10, 2009 12:56 am Post subject: |
|
|
Disciple
Joined: 17 Jun 2008
Posts: 186
|
i checked with a guy from the application team. I was told that there was a physical dataset on Mainframe that stores messages that would be in the queue whose TRIGTYPE I was trying to change. The physical dataset was full, and the tryigger was disabled by one of application's programs.
After the application team emptied the dataset, I could change the TRIGTYPE.
But I don't understand how the program can control the processing of messages. I mean, when the programs turns the trigger off, if there are still messages in the queue, the triggered program will still continue to process all the rest of messages. It's not like the triggered program will suspend processing messages the second the trigger is turned off.
Also I don't understand how changing queue's attribute ca be locked by a program. Is it possible? Looping without commiting? |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
