Therer are a couple of things to tighten up the model and one configuration
attribute that can actually help.
First: After you receive your 2033 do you syncpoint and close the queue
immed? One of the conditions is if the Transaction is running and the queue
is open for I/O.
Second: In a situaion like this, where triggering is "FIRST" it is normal to
issue a MQGET with an apropriate "WAIT" interval specified to offset
possible incoming messages. This helps is resources where the transaction
does not have to be constantly restarted on a secon by second basis. This is
a tuning parameter and is set acording to your application processing flow.
Third: There is an attribute, triggerinterval, that is set on the QMGR level
and can help with retriggering on queues where triggering is set to "FIRST".
There was a M A J O R discussion as to it's use a short while back. This
can(?) help in stances where the application has gone away and messages
arrive on the triggerequeue. Read up on it.
bobbee
>From: Sridhar Ramasubramonian <[EMAIL PROTECTED]>
>Reply-To: MQSeries List <[EMAIL PROTECTED]>
>To: [EMAIL PROTECTED]
>Date: Wed, 14 Aug 2002 15:10:28 +0200
>
>hi listeners...
>
>I am working on the below configuration of MQ...
>* MQ V1.2 on OS/390
>* Application running in CICS TS 1.3
>
>The problem I am facing is with triggering.
>We have established a trigger level of first and on this a
>transaction gets triggered in CICS. The transactions processes
>all messages and then comes down on the QEMPTY condition.
>When we are running full load (with many many messages pumped
>at some constant interval and the transaction getting triggered
>and processing it ) at a point the transaction is not triggered
>and messages pile up after that and do not get triggered.
>
>I inferred after some time that this is caused because the CICS
>transaction comes down probably half a second after the
>SYNCPOINT is done and it found the queue empty.
> In this time CKTI which is the trigger monitoring/triggering
>application saw the transaction up and decided not to trigger this
>transaction.
>
>Has anybody else had this problem. Is this the right inference and
>is there a solution to this problem.
>
>Solutions would be really helpful.
>
>Thanks and regards
>Sridhar
>
>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
_________________________________________________________________
MSN Photos is the easiest way to share and print your photos:
http://photos.msn.com/support/worldwide.aspx
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
