Joined: 22 May 2001 Posts: 1072 Location: Fort Worth, TX, USA
Laurie, you will probably have noticed that there is a setCorrelationId method but no equiavlnet setMsgId method. I think IBM's idea is that each message should have a unique MsgID and that the CorrelationID is free for use for grouping together collections of messages or coordinating replies with corresponding requests.
Can I ask, why do you need to set the MsgID and not the CorrelationID?
Joined: 11 Apr 2001 Posts: 1554 Location: Silicon Valley
We are currently in the process of rewriting an OS/390 COBOL application that was written 5 years ago before MQ for MVS supported logical message groups. The guys who did the original design decided to group messages together by giving them the same MsgId AND CorrelId (don't ask me why). Needless to say this has caused us countless problems because the MsgId is not unique for every message. I would highly advise staying away from any application design that called for creating multiple messages with the same MsgId. I am actually glad to hear that IBM placed this restriction on the AMI interface....
_________________ Brandon Duncan
IBM Certified MQSeries Specialist
MQSeries.net forum moderator
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