| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Correlation ids & IMS transactions |
« View previous topic :: View next topic » |
| Author |
Message
|
| westi |
 Posted: Thu May 10, 2007 1:15 am Post subject: Correlation ids & IMS transactions |
 |
|
Newbie
Joined: 27 Mar 2007
Posts: 4
|
Hi,
The context:
I have developed a Java app using the WMQ 6 JMS client API to do TCP connections to our MQ Manager. Through this I am calling various newly developed IMS transactions (via the IMS bridge).
Most of the IMS transactions are also responsible for putting the reply on the reply queue. This works fine for me as the correlation id is set so I can easily correlate the reply with my request.
The problem:
A few of the transactions uses MQ for communication with other external parties, so eventually my request will be replied from another IMS module in a new context.
As it is done now by the mainframe developer that reply doesn't have any correlation id.
The question:
Is there any way an IMS transaction can control/set the correlation id itself in the reply? Is there a 'standard' solution to this problem?
Please bear in mind that I am not a mainframe developer and only know a few details about IMS/OMTA and the brigde, so I might be asking for the impossible here.
It's just that I am used to the JMS environment where I can control these MQMD fields if I want to, and I find it plausible that IMS would have similar possibilities.
Thanks
John Westi |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Thu May 10, 2007 11:57 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
The default in JMS for the request reply service is:
a) the correlation ID is already set => it is passthrough
b) the correlation ID is not set => put the messageId into the correlationId field.
However MQ has a way to define this in the put options of the request
You can add msgId to CorrelId or CorrelId to CorrelId.
I do not deal in MF apps but I expect that the bridge would respect those settings...
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| westi |
| Posted: Thu May 10, 2007 11:15 pm Post subject: |
|
|
Newbie
Joined: 27 Mar 2007
Posts: 4
|
| fjb_saper wrote: |
The default in JMS for the request reply service is:
a) the correlation ID is already set => it is passthrough
b) the correlation ID is not set => put the messageId into the correlationId field.
However MQ has a way to define this in the put options of the request
You can add msgId to CorrelId or CorrelId to CorrelId.
I do not deal in MF apps but I expect that the bridge would respect those settings...
Enjoy |
Thanks - but my question is in fact mainframe related: the IMS bridge and how a IMS transaction can control the correlation id of the message being sent.
Is this the wrong forum? |
|
| Back to top |
|
|
| cicsprog |
| Posted: Fri May 11, 2007 7:35 am Post subject: |
|
|
Partisan
Joined: 27 Jan 2002
Posts: 347
|
While I'm a MF person, I've never coded an IMS program that communicates with MQ. However, here is a paste from a Power Point I have that may or may not help you:
MQSeries IMS Bridge
�� What you are building is actually an INPUT MQMD
as if the message had come from MQSeries
originally
– The Replyto Queue and Replyto Queue Manager are the
message destination
– The MSGID and CORRELID are the INPUT MSGID and
CORRELID - not necessarily what will be presented to the
MQSeries application
�� You must use the MQMD_REPORT field to specify that the input
MSGID and CORRELID be moved to the corresponding output
MQMD
– The default is that the input MSGID is moved to the output CORRELID
and a new MSGID is created
Obvisouly this speaks to an outbound message from IMS. But, it does shead some light on how MSGID and CORRELID are manipulated. |
|
| 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
|
|
|
|
