John,
You may want to set your queue manager trigger interval to a low value
in order to reset the triggering.
Donna de Peyster

-----Original Message-----
From: Adiraju, Rao [mailto:[EMAIL PROTECTED] 
Sent: Monday, February 09, 2004 4:03 PM
To: [EMAIL PROTECTED]
Subject: Re: Trigger


Hi John

The trigger type "FIRST" activates the trigger when queue depth moves
from 0 to 1.

If I understand correctly, your triggered transaction once started,
immediately disables the "PUT" and starts reading the messages. Once the
messages are exhausted (2033) then it enables the PUT again and
hopefully closing the first triggered transaction.

I wish I know more about your business objective what you are trying to
achieve. I am not sure what's the source of your data queue. If the
messages are coming from external Queue Manager, then upon receiving the
first message, your trigger transaction starts and immediately disables
the "PUTs". Between this interval you may get a few more messages on to
the queue but not many. But then all subsequent messages which are
arriving may end up in the "dead-letter" queue because of PUT disabling.
Is that what you want. On the other hand, if local application is
putting the messages directly, then they will get PUT disabled errors
and their application may take a rollback. In either case, I am not sure
what you are trying to achieve by disabling the "PUTs".

If the business objective of the triggered process is process a
"logical" chunk of messages, I will suggest the following:

1) Keep the trigger type as "FIRST"

2) Triggered process starts when depth moves from 0 to 1.

3) Trigger process DOES NOT disable the PUTS nor TRIGGER TYPE

4) Continuous processing of the "logical" chunk and when the chunk is
finished then it starts itself another instance of it. If gets 2033 then
takes a normal end in which case MQ Manager will start another instance
of triggered process when next time queue depth moves from 0 to 1.

As I said earlier if you can give us the business requirement what you
are trying to achieve, might help in providing more accurate solution.

Cheers

Rao Adiraju
WebSphere MQ Specialist
The National Bank of NZ Ltd.
Tel:  +64-4-494 4299
Fax: +64-4-802 8509
Mbl: +64-211-216-116





-----Original Message-----
From: Dawson, John [mailto:[EMAIL PROTECTED]
Sent: 10 February 2004 4:21 AM
To: [EMAIL PROTECTED]
Subject: Trigger

Hey Folks,

  I have a triggered queue, triggering on first. The 'puts' for the
queue is disabled because the program, acting upon a message, has to
stop the processing, inside the loop that is getting messages until a
return code of 2033. Because of this, messages will remain on the queue.

  When the 'puts' on the queue  is re-enabled, will the remaining
messages on the queue force the trigger to start again or will it take a
new message arriving on the queue to start the triggering.

  What if the triggering is turned off and then on at the same time as
the 'puts' are re-enabled?


Thanks everyone,

John Dawson

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive

This communication is confidential and may contain privileged material.
If you are not the intended recipient you must not use, disclose, copy
or retain it. If you have received it in error please immediately notify
me by return email and delete the emails. Thank you.

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive

Reply via email to