| Author |
Message
|
| wssuite01 |
 Posted: Tue Jan 25, 2005 2:14 am Post subject: MQOutput Node : New Correlation ID bug? |
 |
|
Newbie
Joined: 07 Jan 2005
Posts: 8
|
Hi,
I've got a very simple message flow, consisting of an
MQInput node whose out terminal is connected to an
MQOutput node. I've only checked the box New
Correlation ID on the MQ Output node. All other fields
have default values.
But, I don't see a new correlation id being generated
for the output messages.
The New Message ID option however seems to work ..
Is this a bug or am i missing something?
Thanks,
Samuel |
|
| Back to top |
|
 |
| kirani |
| Posted: Tue Jan 25, 2005 11:23 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
What version of WBIMB/WMQI are you using?
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
|
| mqmhr |
| Posted: Wed Jan 26, 2005 1:19 am Post subject: |
|
|
Centurion
Joined: 28 Dec 2004
Posts: 105
|
I am using WBIMB 5 with FP2.
Whenever, the option "New Correlation Id" is checked, the output message has a correlation id with all blanks. However, if we do not check the option, the correlation id is passed without any change. I do not think a "new" non-all blanks correlation id is ever generated for the output message. In other words, the MQOutput Node program seems to use a MQCI_NONE in its MQPMO instead of MQCI_NEW_CORREL_ID. Am not sure if this is a bug or an intended functionality. If it is the latter, the name "New Correlation Id" is misleading. |
|
| Back to top |
|
|
| TonyD |
| Posted: Wed Jan 26, 2005 2:15 pm Post subject: |
|
|
Knight
Joined: 15 May 2001
Posts: 540
Location: New Zealand
|
As I posted to this thread which was also on the MQ listserver:
| Quote: |
Worked for me:
Input Message ID:
X'414d51205444424b31514d2020202020b071f44120011702'
Input Correlation ID:
X'000000000000000000000000000000000000000000000000'
Set OutputRoot = InputRoot (Compute node)
Output Message ID:
414D51205444424B31514D2020202020B071F44120011702
Output Correlation ID:
414D51205444424B31514D2020202020B071F44120011802
Tried again with just MQInput -> MQOutput:
Output Message ID:
414D51205444424B31514D2020202020B071F44120011703
Output Correlation ID:
414D51205444424B31514D2020202020B071F44120011803
|
I am on FP4...don't know if that makes a difference. |
|
| Back to top |
|
|
| kirani |
| Posted: Wed Jan 26, 2005 2:33 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
It'd be better to install FP4 and test this. FP4 is much more stable than FP2.
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
|
| Craig B |
| Posted: Mon Feb 21, 2005 2:04 am Post subject: |
|
|
Partisan
Joined: 18 Jun 2003
Posts: 316
Location: UK
|
Hi,
You encountered a problem reported by APAR IC37169, and this was fixed in V5 FP03. Therefore, since you are at FP02, you are still encountering this problem.
_________________
Regards
Craig |
|
| Back to top |
|
|
|
|
