|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
IMS bridge |
« View previous topic :: View next topic » |
Author |
Message
|
gsrinidhi |
Posted: Wed Sep 06, 2006 1:13 pm Post subject: IMS bridge |
|
|
Novice
Joined: 17 Jan 2006 Posts: 17 Location: mi
|
Let me tell you some details of bridge....
1)
For IMS bridge the distributed application who wants to trigger mainframe online transaction they would need to specify the name of transaction inside the message each time.
Well so every application now needs to remember the transaction name with code change and it was not the case with some java adapters. so company avoids bridge.
2) when IMS transaction is down but bridge & ims are up, even though there is no error in the format of message, the message would be put to dlq. This would have MQRC_UNKNOWN_X00000XXX error code which is again unable to trap by IBM dlq routine.
Do you manullay code for this? Thats not prefferable.
Any better solution?
Manager is struck with java architects to favour IBM product. huh but I guess little chance...
Srini |
|
Back to top |
|
 |
LuisFer |
Posted: Wed Sep 06, 2006 8:44 pm Post subject: Re: IMS bridge |
|
|
 Partisan
Joined: 17 Aug 2002 Posts: 302
|
I don't understand the finally of this post but..
gsrinidhi wrote: |
1)
For IMS bridge the distributed application who wants to trigger mainframe online transaction they would need to specify the name of transaction inside the message each time.
Well so every application now needs to remember the transaction name with code change and it was not the case with some java adapters. so company avoids bridge.
|
The MQBrigde uses IMS's OTMA to put Tx on IMS Queues, this tx is not triggered in any case. This one emulates a typical 3270 or LU tx.
gsrinidhi wrote: |
2) when IMS transaction is down but bridge & ims are up, even though there is no error in the format of message, the message would be put to dlq. This would have MQRC_UNKNOWN_X00000XXX error code which is again unable to trap by IBM dlq routine.
|
When the TX is stopped the IMS responses with an DFS065 XX:XX:XX TRAN/LTERM STOPPED to the ReplyQ, and the original Messages is put on DLQ, with the OTMA NAK (in this case x'146' (326 Dec - Tran/Lterm)stoped)) this one is not an MQ error (as 2051,2053,...)
Regards |
|
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
|
|
|
|