If I remember correctly with TRIGTYPE(EVERY), the trigger message is generated when a message arrives on the queue however if the transaction abends and the message is backed out a new trigger message is not generated (that is strictly from memory and it may have failed me). That would mean that special provisions would have to be made for abend conditions if you are absolutely depending on 1 trigger message per message on the queue and the application reads one and only one message.
I remember the "conditions for a trigger event" discussion in the APG discussing the generation of another trigger message in the case of an abend condition only occurring with TRIGTYPE(DEPTH or FIRST) and not TRIGTYPE(EVERY).
Cheers... Jim Nuckolls
Jeff Horner wrote:
Rick,
The transaction is not disabled.
The program that the transaction executes is not disabled.
I disabled another program that is called via a COBOL CALL to cause an abend. I needed to test this condition, but it is not working out so well. Here is more details of what is happening in the process.
Transaction WXYZ points to program PGRM001. Both are enabled.
PGRM001 is triggered by CKTI and it opens the queue with open options INPUT-SHARED, INQUIRE and FAIL-IF-QUIESCING. It then does and MQGET to get the message from the queue that caused the trigger condition. It uses get options of WAIT,CONVERT,FAIL-IF-QUIESCING and SYNCPOINT. Then it does a COBOL CALL to program PGRM999. PGRM999 is disabled in CICS. This causes the transaction WXYZ to abend in CICS with and ABEND CODE of 4038. Then the transaction WXYZ is never triggered again.
I am at a loss at what is happening.
>From: Rick Tsujimoto >Reply-To: MQSeries List >To: [EMAIL PROTECTED] >Subject: Re: MQ v5.3 OS/390 Trigger Problem >Date: Fri, 26 Sep 2003 09:23:57 -0400 > >Is the program or transid disabled? > > > > > Jeff Horner > < [EMAIL PROTECTED] To:>> AIL.COM> cc: > Sent by: Subject: MQ v5.3 OS/390 Trigger Problem > MQSeries List > <>> en.AC.AT> > > > 09/26/2003 02:51 > AM > Please respond > to MQSeries List > > > > > >I have a CICS transaction that is triggered by the CICS trigger monitor >(CKTI). >The local queue attribute for trigger type is EVERY. >When the transaction is triggered it gets a message off the queue under a >syncpoint (MQGMO_SYNCPOINT). It then abends and the message is rolled back >to the >originating local queue. > >The problem is that the trigger monitor does not start the CICS transaction >again (no trigger >message is put on the initiation queue). I know the transaction does not >start again because >the use count of the program is not incremented. Does anyone know what >could cause this problem as I have used this same logic before and have not >came across this problem in the past? > >The CICS abend is a 4038. I thought I remembered something about this abend >in CICS has something to do with this problem. > >Share your photos without swamping your Inbox. Get Hotmail Extra Storage >today! >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
------------------------------------------------------------------------ Instant message in style with MSN Messenger 6.0. Download it now FREE! <http://g.msn.com/8HMBENUS/2734??PS=> 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
