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

MQ: Problem with triggering a transaction


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

New User


Joined: 30 Jun 2009
Posts: 3
Location: hyderabad

PostPosted: Thu Jul 02, 2009 12:28 pm
Reply with quote

Hi,
We are facing some issue with triggering of CICS transaction when message is put on to a Queue on our Mainframe.

About application: We have some application which can be segregated into Client (Involves only CICS) and Server (one CICS module and rest all is DB2). when tested individually Client application is able to put the message into the static queue. This static Queue is connected with initiation queue which is monitored by CICS. The message entry into static queue should invoke the transaction of Server application. But this is not happening. I even cross checked the Server application even. This is also working fine. But when i execute total as one application server side application is not getting invoked.

Note: we are executing a delay module with an interval of 10 sec and client application will tried to get the message from the dynamic queue, which should be populated by the server application when triggered.


Need your inputs on this.

Thanks in advance,
Visu
Back to top
View user's profile Send private message
Bill Dennis

Active Member


Joined: 17 Aug 2007
Posts: 562
Location: Iowa, USA

PostPosted: Thu Jul 02, 2009 8:31 pm
Reply with quote

Examine the local queue to be sure TRIGGER in ON and TRIGTYPE is FIRST.
Back to top
View user's profile Send private message
visu319

New User


Joined: 30 Jun 2009
Posts: 3
Location: hyderabad

PostPosted: Fri Jul 03, 2009 11:05 am
Reply with quote

Hi Bill,
The local queue definition looks fine. The two parameters which u suggested are defined like this.

Trigger type . . . . . . : E F=First, E=Every, D=Depth, N=None
Trigger set . . . . . . : Y Y=Yes, N=No

I am still facing this issue.

Thanks,
Visu
Back to top
View user's profile Send private message
Garry Carroll

Senior Member


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

PostPosted: Fri Jul 03, 2009 1:26 pm
Reply with quote

Also, check the local queue to see that it references a PROCESS definition which specifies the CICS transaction to be executed.

Garry.
Back to top
View user's profile Send private message
visu319

New User


Joined: 30 Jun 2009
Posts: 3
Location: hyderabad

PostPosted: Fri Jul 03, 2009 4:57 pm
Reply with quote

Garry Carroll wrote:
Also, check the local queue to see that it references a PROCESS definition which specifies the CICS transaction to be executed.

Garry.


Hi Garry,
I checked that Process that is referred on the initiation queue, the definition of the same contains application type as CICS and trans id. I checked with CKBM transaction, the same initiation queue is being monitored by it.

I have one question here. My transaction module that should be triggered contain some code in cobol and only EXEC CICS RETURN statement. There are no SEND or RECEIVE command used.

Please let me know, if there could be any issue with transaction module.

Thanks,
Visu
Back to top
View user's profile Send private message
Garry Carroll

Senior Member


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

PostPosted: Fri Jul 03, 2009 5:11 pm
Reply with quote

Hi Visu,
Have you checked the program for that transaction using CEMT ? If it's being triggered, you should see its use count increment if it's being executed.
It's surprising that the only EXEC CICS in the code is the RETURN - is m there any EXEC SQL ? How does the CICS application record anything it does?

Garry.
Back to top
View user's profile Send private message
genesis786

Active User


Joined: 28 Sep 2005
Posts: 210
Location: St Katherine's Dock London

PostPosted: Mon Jul 06, 2009 5:00 pm
Reply with quote

I try following troubleshooting steps in such case:

1. Check if the Msg is landing in the Q. (disable the trigger and do MQBR)
2. Check if the trigger is enabled on the Q.
3. Check if the process definition is right or not. (ie cics set up should be done for that process)
4. Check if the process/transaction is enabled in CICS.
5. Check if the program is enabled or not.
6. Check job log for the CICS transaction if the problem persists.
7. If none works, check with peers / those who know icon_smile.gif


apart from that:

Trigger Type - E isn't really recommended by our middleware admins. They recommend using F and then using the program to read through the end of queue. Anyhow, I am sure you must have a reason for that.
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 Map Vols and Problem Dataset All Other Mainframe Topics 2
No new posts How to identify the transaction categ... IMS DB/DC 3
No new posts z/vm installation problem All Other Mainframe Topics 0
No new posts Start CICS transaction every day at 2AM CICS 4
No new posts Job scheduling problem. JCL & VSAM 9
Search our Forums:

Back to Top