| Author |
Message
|
| mahesh_klm |
 Posted: Sun Jul 08, 2012 4:09 am Post subject: |
 |
|
Novice
Joined: 21 Jun 2012
Posts: 13
Location: India/Bangalore
|
| Sorry for the wrong info as the issue was with the code. What i was informed during positing above one was there is a datapower setup which sweeps off the message from Q at the moment we insert message to Q. So we are not able to view the details. But data power team was not able to see the message. So that set had been paused and we put the message again and failed in that. So analyzed the code and we had to get the MQPMO_options to No sync point + New correlation ID. And we ware able to see the message in Q in the XML format. Now we are setting up expire interval for this. And same program is having an MQGET step also. We need to have an ideal wait interval so that the response from destination system needs to be recorded back in mainframe system. Once again sorry to put wrong information. |
|
| Back to top |
|
 |
| bruce2359 |
| Posted: Sun Jul 08, 2012 5:05 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| mahesh_klm wrote: |
| Sorry for the wrong info as the issue was with the code. What i was informed during positing above ... |
Apology not necessary. Problem-source identification (PSI) is an iterative process: you tell us what you know; we ask more questions;repeat.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| mahesh_klm |
| Posted: Sun Jul 08, 2012 6:37 am Post subject: |
|
|
Novice
Joined: 21 Jun 2012
Posts: 13
Location: India/Bangalore
|
Thanks Bruce. I may come back with questions on MQGET  |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Sun Jul 08, 2012 7:52 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| mahesh_klm wrote: |
| Thanks Bruce. I may come back with questions on MQGET |
Stop by any time.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| mahesh_klm |
| Posted: Thu Jul 26, 2012 10:06 am Post subject: MQGET |
|
|
Novice
Joined: 21 Jun 2012
Posts: 13
Location: India/Bangalore
|
| Hi Guys. As expected i am back with issues n MQGET. I am using a correlation id check to match the request and response. Our architecture is in such a way that we are sending from mainframe to a middle ware system and to a target system. Response from target to middle ware and back to mainframe. When we check the message and corrrelids of response, it is not at all matching with the request. Middleware is sending us the same as what we are sening in request. Do i need to give any convert option while receiving? |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Jul 26, 2012 12:08 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
No but you should be aware that correlation Id like message id follows the pattern of anonymous identifier. Which means you should not have any text or "meaningful" value. These identifiers are defined as MQByte(24) IIRC and this means a byte array of 24 bytes.
There is no translation or CCSID impact... whatever the language, a byte is a byte is a byte...
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| mahesh_klm |
| Posted: Fri Jul 27, 2012 7:36 pm Post subject: |
|
|
Novice
Joined: 21 Jun 2012
Posts: 13
Location: India/Bangalore
|
| The issue had been solved. Message id in request was converted to correlation id in response. WE got a confusion previously as the middleware log was showing message id and correlation id same as we are sending. But those logs were showing values before executing MQ steps. Tried MQGET with correlation id as message id of request and match correlation id option. it worked. |
|
| Back to top |
|
|
|
|
