| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| CICS transaction error |
« View previous topic :: View next topic » |
| Author |
Message
|
| Sonali |
 Posted: Tue Jun 01, 2004 5:01 am Post subject: CICS transaction error |
 |
|
Novice
Joined: 08 Apr 2004
Posts: 22
|
| What can be cause of CICS transaction error??In my message flow ,a CICS transaction error has occured and I dont understand what should I look at?? |
|
| Back to top |
|
 |
| Sonali |
| Posted: Tue Jun 01, 2004 5:17 am Post subject: |
|
|
Novice
Joined: 08 Apr 2004
Posts: 22
|
| Please help me.I am in urgent need to know possible cause of CICS transaction error. |
|
| Back to top |
|
|
| Missam |
| Posted: Tue Jun 01, 2004 5:55 am Post subject: |
|
|
Chevalier
Joined: 16 Oct 2003
Posts: 424
|
| Hi you can use the serach button above with search option CICS and transaction and error.you can see some results. |
|
| Back to top |
|
|
| Sonali |
| Posted: Tue Jun 01, 2004 6:03 am Post subject: |
|
|
Novice
Joined: 08 Apr 2004
Posts: 22
|
| Matched results doesn't help me. |
|
| Back to top |
|
|
| Zteve |
| Posted: Tue Jun 01, 2004 8:00 am Post subject: CICS Transaction Error in Message Flow |
|
|
Newbie
Joined: 01 Jun 2004
Posts: 2
Location: IBM Hursley
|
Sonali, can you explain a little more about your problem? Are you using a CICS node in your flow, or using the CICS/MQ Bridge? Or is this all gobbledegook to you?
Perhaps you could append here the full text of the error message you are seeing.
_________________
Steve Powell, Hursley Park |
|
| Back to top |
|
|
| Sonali |
| Posted: Tue Jun 01, 2004 8:58 am Post subject: |
|
|
Novice
Joined: 08 Apr 2004
Posts: 22
|
| ya,I have 2 flows for request and reply.Request flow is getting XML file,converting it to cobol and sends it to mainframe.On the mainframe side,a reply message is constructed and send to reply-queue(mentioned while sending the request).After getting this reply message.a filter node is checking if any CICS transaction error occured or not.If occured,then a compute node constructs XML error message and sends it to queue.And error message matches with this compute node's statements,thats how i interpreted that CICS transaction error occured. |
|
| Back to top |
|
|
| Zteve |
| Posted: Wed Jun 02, 2004 2:46 am Post subject: CICS Transaction Error |
|
|
Newbie
Joined: 01 Jun 2004
Posts: 2
Location: IBM Hursley
|
Well, there is no response to this post after all this time -- so I hope your problem has gone away, Sonali.
I'll leave this up, though, for other people. 
| Sonali wrote: |
| ya,I have 2 flows for request and reply.Request flow is getting XML file,converting it to cobol and sends it to mainframe.On the mainframe side,a reply message is constructed and send to reply-queue(mentioned while sending the request).After getting this reply message.a filter node is checking if any CICS transaction error occured or not.If occured,then a compute node constructs XML error message and sends it to queue.And error message matches with this compute node's statements,thats how i interpreted that CICS transaction error occured. |
From the above, I assume that you are using MQ to send a message to the CICS system, and to receive the reply message. The transaction is then triggered on CICS by the MQ/CICS bridge mechanism, which handles the reply message.
If you are receiving a reply message, then this is either generated by your CICS transaction (and contains whatever the application says it should) or else it is generated by the MQ/CICS bridge mechanism in the event of an error. Since your reply flow is reporting a 'CICS Transaction' error, I'm assuming this is a standard reply message.
The reply is sent (by MQ/CICS Bridge) even if the transaction backs out or ABENDs, and there are a number of fields in the reply message explaining what went wrong. You should look in the MQ APR (Application Programmer's Reference) in the section called CICS Information Header, to interpret those fields. No doubt your filter is doing just that. The values of those fields are a bit more informative than just 'error', but not a lot. At least you will be able to tell if the transaction abended, or if the bridge failed, or if the program is missing or disabled, and so on.
The story varies slightly depending upon whether you are using a DPL or 3270 variant of the MQ/CICS Bridge, but the reference should help you in either case.
Does that help? If you discover that the CICS transaction itself failed, the next place to look is on the CICS system -- where there should be some messages, and/or diagnostic information, like a transaction dump. In the worst case you could switch CICS tracing on (see your CICS administrator to do this selectively) or even interactively debug the COBOL trasnaction program at a CICS terminal, while running an experimental flow.
Good luck, and please report your progress back here.
_________________
Steve Powell, Hursley Park |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
