View previous topic :: View next topic
|
Author |
Message |
vinu78
Active User
Joined: 02 Oct 2008 Posts: 179 Location: India
|
|
|
|
Hi All,
We are getting the data in MQSERIES queue from some other system. Mainframe COBOL program gets those messages, processes it and then puts back to the sender with message as "Successfully processed" along with Correlation ID. My concern is that I am not getting the valid Correlation ID value.
Steps that I did
- Gets the message from queue with syntax as
COMPUTE MQGMO-OPTIONS = (MQGMO-NO-SYNCPOINT +
MQGMO-ACCEPT-TRUNCATED-MSG +
MQGMO-CONVERT +
MQGMO-WAIT).
CALL WS-MQGET USING WS-HCONN
WS-HOBJ
MQMD
MQGMO
WS-CTCREC-DATALENGTH
MQ-INPUT
WS-RETURN-QMSG-DATALENGTH
WS-COMPLETION-CODE
WS-REASON-CODE.
- Processes the message and put back the message as Successful to the sender
COMPUTE MQPMO-OPTIONS =
(MQPMO-NO-SYNCPOINT
+ MQPMO-NEW-MSG-ID
+ MQPMO-NEW-CORREL-ID
+ MQPMO-DEFAULT-CONTEXT)
CALL 'MQPUT1' USING WS-HCONN
MQOD
MQMD
MQPMO
WS-REPLY-MSG-DATALENGTH
WS-FORMATTED-MQREPLY-MSG
WS-COMPLETION-CODE
WS-REASON-CODE.
While checking the MQPMO-NEW-CORREL-ID value, it is given as standard value 128. I am not sure why Correlation ID is not getting changed ?
Please help me.
Thanks
Vinu |
|
Back to top |
|
|
Garry Carroll
Senior Member
Joined: 08 May 2006 Posts: 1193 Location: Dublin, Ireland
|
|
|
|
Following standard MQ reply processing, you should move the inbound MSG-ID to the reply message's MQMD.CorrelId. The requesting program would then issue its MQGET specifying the request MSG-ID as the reply's CORRELID. What advantage would you have in generating a new unique CORRELID on the reply?
Garry |
|
Back to top |
|
|
|