IBM Mainframe Forum Index
 
Log In
 
IBM Mainframe Forum Index Mainframe: Search IBM Mainframe Forum: FAQ Register
 

Infinite Trigger of MQ attached CICS Transaction


IBM Mainframe Forums -> Java & MQSeries
Post new topic   Reply to topic
View previous topic :: View next topic  
Author Message
Nimesh.Srivastava

New User


Joined: 30 Nov 2006
Posts: 78
Location: SINGAPORE

PostPosted: Wed Nov 03, 2010 9:08 am
Reply with quote

Hi All,
we are facing a problem in our shop
Setup
there is a local MQ defined on mainframe linked to another remote MQ in open system
this local MQ MQA1 is linked to a CICS transaction IXY1 with trigger level 1

Problem
the open system guys written 2 items on the MQ MQA1 and this initiated my transaction IXY1 in the CICS region. Flow went like below
Code:

MQCONN
MQOPEN
MQGET - MQA1
program ABEND

upon exit the no. of items on the MQA1 remain as 2 as seen from PQEDIT

now what happens is transaction IXY1 is initiated again and as everytime program abends this triggering goes into an infinite loop

is there a way to stop this infinite trigger?
basically, what I want is below flow
1/ 2 items written to MQA1
2/ CICS transaction IXY1 is initiated read one item from MQ and then abends
3/ no trigger of IXY1 again
4/ no of items on MQA1 remains as 2
5/ if another item is written onto MQA1 i.e third then only the CICS transaction IXY1 should be initiated

Thanks in advance
Nimesh

PS: my CICS intrapartition TD queues with trigger level 1 behave as above
Back to top
View user's profile Send private message
Garry Carroll

Senior Member


Joined: 08 May 2006
Posts: 1193
Location: Dublin, Ireland

PostPosted: Thu Nov 04, 2010 3:20 pm
Reply with quote

I think you may need to review how you have configured triggering and what type of messages are in use.

You say
Quote:

this local MQ MQA1 is linked to a CICS transaction IXY1 with trigger level 1

MQ supports TRIGGER=NONE, TRIGGER=FIRST, TRIGGER=EVERY or TRIGGER=DEPTH. Which are you using? TRIGGER=DEPTH with DEPTH set to 1?

If using depth with depth set to 1, I suggest changing to TRIGGER=EVERY. If a task abends, any message retrieved with MQGMO_SYNCPOINT will be restored to the queue so triggering is likely to be re-activated isf using depth.


Other information that may be relevant...
Are your trigger messages persistent? Are your application messages persistent? Are you issuing MQGET with or without SYNCPOINT?

There are a number of factors that affect how triggering works.

Garry.
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic View Bookmarks
All times are GMT + 6 Hours
Forum Index -> Java & MQSeries

 


Similar Topics
Topic Forum Replies
No new posts Using API Gateway from CICS program CICS 0
No new posts Calling an Open C library function in... CICS 1
No new posts How to 'Ping' a CICS region in JCL CICS 2
No new posts Parallelization in CICS to reduce res... CICS 4
No new posts How to identify the transaction categ... IMS DB/DC 3
Search our Forums:

Back to Top