Author |
Message
|
guest468 |
Posted: Tue May 19, 2009 10:32 am Post subject: MQGET is throwing MQRC_FORMAT_ERROR |
|
|
Centurion
Joined: 30 May 2006 Posts: 146 Location: NY
|
Hi,
I am seeing MQRC_FORMAT_ERROR error while trying to get an EBCDIC message using MQGMO_CONVERT gmo option.
Now the message is coming with null as MQMD.Format. I am aware that format should be MQSTR for the convert to work. But Mainframe is not going to change anything in their side to make this happen (for several valid reasons ). So just wondering if there is anyway I can still get it converted?
Thanks for the help.
Dave |
|
Back to top |
|
 |
mqjeff |
Posted: Tue May 19, 2009 10:33 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
MQ can not do any conversion on messages that have null format. |
|
Back to top |
|
 |
zpat |
Posted: Tue May 19, 2009 11:13 am Post subject: |
|
|
 Jedi Council
Joined: 19 May 2001 Posts: 5866 Location: UK
|
MQPUT application should set MQMD.format as MQSTR.
The IBM default value of none causes so much grief!
There is no valid reason not to fix the sending application - really, it is nonsense to work around this.
In any case you can't short of coding an exit to modify the MQMD which is far more effort than fixing the application.
In the world of the truly insane, you could get it without conversion, put it back on the queue with a correct MQMD and get it again (matching Msgid) with conversion or just convert it manually in the program.
You could also pass it through a message broker and convert it in ESQL with CAST. |
|
Back to top |
|
 |
guest468 |
Posted: Tue May 19, 2009 12:17 pm Post subject: |
|
|
Centurion
Joined: 30 May 2006 Posts: 146 Location: NY
|
Thanks zpat and Jeff for the help.
I will go with WMB to do this. Actually as of now; the routing is taking place through broker only. But following up with the change ticket cycle for this is going to be a headache though
Thanks |
|
Back to top |
|
 |
mqjeff |
Posted: Tue May 19, 2009 12:35 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
If you're already passing messages through broker, then the best thing is to pass them through a tiny flow that MQInput->Compute->MQOutput to change the MQMD.Format as zpat mentioned.
Then everything else works normally. |
|
Back to top |
|
 |
guest468 |
Posted: Fri May 22, 2009 5:56 am Post subject: |
|
|
Centurion
Joined: 30 May 2006 Posts: 146 Location: NY
|
Hi
sorry guys to reopen this topic.
Actually when I browsed the same message using MQMON it displayed it in ASCII. Just wondering if MQMON does some kind of workaround?
Thanks |
|
Back to top |
|
 |
zpat |
Posted: Fri May 22, 2009 7:19 am Post subject: |
|
|
 Jedi Council
Joined: 19 May 2001 Posts: 5866 Location: UK
|
MO71 browse does convert, right click to select convert on or off on the browse display (then refresh).
I always thought it was using MQGET with CONVERT on the BROWSE. You could email the developer (Paul Clarke). |
|
Back to top |
|
 |
|