Author |
Message
|
kumarbai |
Posted: Fri May 24, 2013 6:25 am Post subject: |
|
|
Apprentice
Joined: 24 May 2013 Posts: 45
|
how can i disable MQGMO_CONVERT in my MQ q manager? |
|
Back to top |
|
 |
kumarbai |
Posted: Fri May 24, 2013 6:26 am Post subject: |
|
|
Apprentice
Joined: 24 May 2013 Posts: 45
|
PeterPotkay wrote: |
Your sending messages formated for IMS to a UNIX server? |
I am receiveing messages from IMS bridge |
|
Back to top |
|
 |
PeterPotkay |
Posted: Fri May 24, 2013 6:38 am Post subject: |
|
|
 Poobah
Joined: 15 May 2001 Posts: 7722
|
kumarbai wrote: |
PeterPotkay wrote: |
Your sending messages formated for IMS to a UNIX server? |
I am receiveing messages from IMS bridge |
Unless you have an IMS application running on your UNIX server accessed by an OTMA bridge queue on your UNIX server (you don't), it is not correct to send messages to the Unix server with that format.
Review this and think about your sending application, the one that sends to the mainframe.
http://publib.boulder.ibm.com/infocenter/wmqv7/v7r0/topic/com.ibm.mq.csqzak.doc/fr12890_.htm _________________ Peter Potkay
Keep Calm and MQ On |
|
Back to top |
|
 |
bruce2359 |
Posted: Fri May 24, 2013 6:39 am Post subject: |
|
|
 Poobah
Joined: 05 Jan 2008 Posts: 9469 Location: US: west coast, almost. Otherwise, enroute.
|
kumarbai wrote: |
how can i disable MQGMO_CONVERT in my MQ q manager? |
The application consuming (getting) the messages asks for conversion by specifying MQGMO_CONVERT in the MQGET call options. It is not a qmgr option. So, don't specify MQGMO_CONVERT. _________________ 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 |
|
 |
mqjeff |
Posted: Fri May 24, 2013 6:42 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
bruce2359 wrote: |
kumarbai wrote: |
how can i disable MQGMO_CONVERT in my MQ q manager? |
The application consuming (getting) the messages asks for conversion by specifying MQGMO_CONVERT in the MQGET call options. It is not a qmgr option. So, don't specify MQGMO_CONVERT. |
It's an App Server, so it's likely using JMS, so it's likely asking for a TextMessage, which will do conversion, instead of a BytesMessage, which won't.
But since it's the queue manager throwing the error, it's possible that CONVERT is set on the relevant channel, rather than being left to the application. |
|
Back to top |
|
 |
bruce2359 |
Posted: Fri May 24, 2013 6:43 am Post subject: |
|
|
 Poobah
Joined: 05 Jan 2008 Posts: 9469 Location: US: west coast, almost. Otherwise, enroute.
|
kumarbai wrote: |
yes MQMD.Format was set to "MQIMS.
Can you help how to resolve? |
This is in the application that produces (puts) the message? Is the format field literally set to "MQIMS"? Or is it "MQFMT_IMS"? _________________ 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 |
|
 |
hughson |
Posted: Fri May 24, 2013 6:46 am Post subject: |
|
|
 Padawan
Joined: 09 May 2013 Posts: 1959 Location: Bay of Plenty, New Zealand
|
PeterPotkay wrote: |
Your sending messages formated for IMS to a UNIX server? |
If you send a message *TO* the IMS Bridge with the IMS Header on it, the reply will come back with the IMS Header on it too.
Cheers
Morag _________________ Morag Hughson @MoragHughson
IBM MQ Technical Education Specialist
Get your IBM MQ training here!
MQGem Software |
|
Back to top |
|
 |
PeterPotkay |
Posted: Fri May 24, 2013 6:56 am Post subject: |
|
|
 Poobah
Joined: 15 May 2001 Posts: 7722
|
hughson wrote: |
PeterPotkay wrote: |
Your sending messages formated for IMS to a UNIX server? |
If you send a message *TO* the IMS Bridge with the IMS Header on it, the reply will come back with the IMS Header on it too.
|
OK. I see that here:
http://publib.boulder.ibm.com/infocenter/wmqv7/v7r0/topic/com.ibm.mq.csqzal.doc/fg15990_.htm
But if the MQIIH ReplytoFormat field is set appropriately does that mean the reply comes back with the MQMD_Format set to MQSTR allowing conversion to happen on the reply message by the Unix Queue manager, but the app still needs to deal with the IIH header that will be present ahead of the app data in the message buffer? _________________ Peter Potkay
Keep Calm and MQ On |
|
Back to top |
|
 |
kumarbai |
Posted: Fri May 24, 2013 7:00 am Post subject: |
|
|
Apprentice
Joined: 24 May 2013 Posts: 45
|
Queue managers log files filling up with warning messages
When an application gets a message using the MQGMO_CONVERT option, the queue manager attempts to invoke a data conversion exit to convert the data before returning the message. If an application is using the MQMD Format field to specify user data rather than a built-in format, and there is no data conversion exit for that format, warning messages are written to the queue manager error logs for each message which is requested. The message is still passed to the application in this circumstance, although no conversion has been performed on the message.
The property and valid values which is used to specify if the queue manager is to convert the message (through the use of the MQGMO_CONVERT option on the internal MQGET call), or if the message should be received without queue manager conversion, is shown ibelow
Property :
RECEIVECONVERSION
Possible Value:
1. CLIENT_MSG : Message conversion performed in the client.
2.QMGR : MQGMO_CONVERT specified on MQGET commands, queue manager performs conversion.
If using the WebSphere Application Server JNDI namespace, this property can be configured using the Administration Console, as a custom property specified on the Destination (Resources->JMS->Queues->[queue]->Custom properties->New).
Can someone confirm if above things are the right steps to do? |
|
Back to top |
|
 |
mqjeff |
Posted: Fri May 24, 2013 7:08 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
kumarbai wrote: |
Can someone confirm if above things are the right steps to do? |
Not without knowing what counts as "the right steps" at your particular site with your particular configuration under your particular change management rules for your particular application for your particular WAS configuration.
talk to your MQ admin.
Edit, to be more clear all this will do is prevent the queue manager from throwing errors.
This will then cause the application to start receiving messages that it previously was not receiving, because the queue manager was failing to deliver them because it could not convert them.
This almost certainly means that the person having to deal with a lot of errors in their log files stops being the MQ administrator and starts being either the WAS administrator or the application team.
Last edited by mqjeff on Fri May 24, 2013 7:24 am; edited 1 time in total |
|
Back to top |
|
 |
hughson |
Posted: Fri May 24, 2013 7:15 am Post subject: |
|
|
 Padawan
Joined: 09 May 2013 Posts: 1959 Location: Bay of Plenty, New Zealand
|
kumarbai wrote: |
Can someone confirm if above things are the right steps to do? |
I didn't actually understand from your post what you planned to change?
Did you see my question about the version of MQ you are using? About DC of IMS Header being part of the product more recently?
Cheers
Morag _________________ Morag Hughson @MoragHughson
IBM MQ Technical Education Specialist
Get your IBM MQ training here!
MQGem Software |
|
Back to top |
|
 |
kumarbai |
Posted: Fri May 24, 2013 7:25 am Post subject: |
|
|
Apprentice
Joined: 24 May 2013 Posts: 45
|
|
Back to top |
|
 |
bruce2359 |
Posted: Fri May 24, 2013 7:36 am Post subject: |
|
|
 Poobah
Joined: 05 Jan 2008 Posts: 9469 Location: US: west coast, almost. Otherwise, enroute.
|
When you are asked a question, please answer it precisely. For example, I asked you
bruce2359 wrote: |
Is the format field literally set to "MQIMS"? Or is it "MQFMT_IMS"? |
"MQFMT_IMS" is an MQ-supported format type. "MQIMS" is a string of characters that names a conversion utility to be invoked when the message is consumed from the destination queue if the application specifies MQGMO_CONVERT. _________________ 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 |
|
 |
hughson |
Posted: Fri May 24, 2013 7:57 am Post subject: |
|
|
 Padawan
Joined: 09 May 2013 Posts: 1959 Location: Bay of Plenty, New Zealand
|
mqjeff wrote: |
Edit, to be more clear all this will do is prevent the queue manager from throwing errors.
This will then cause the application to start receiving messages that it previously was not receiving, because the queue manager was failing to deliver them because it could not convert them. |
Failure to data convert the message will not result in the message not being delivered. If the application is already coping with the unconverted message, it may be a no-op to turn off conversion. However, we don't know whether it is or isn't coping? _________________ Morag Hughson @MoragHughson
IBM MQ Technical Education Specialist
Get your IBM MQ training here!
MQGem Software |
|
Back to top |
|
 |
mqjeff |
Posted: Fri May 24, 2013 8:01 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
hughson wrote: |
mqjeff wrote: |
Edit, to be more clear all this will do is prevent the queue manager from throwing errors.
This will then cause the application to start receiving messages that it previously was not receiving, because the queue manager was failing to deliver them because it could not convert them. |
Failure to data convert the message will not result in the message not being delivered. If the application is already coping with the unconverted message, it may be a no-op to turn off conversion. However, we don't know whether it is or isn't coping? |
or, why I shouldn't be responding to posts when I'm distracted by ten other things...
but an MQRC !=0 or an MQCC !=0 may cause the JMS layer or the app layer on top of the JMS layer to discard the message silently.
But as you say, we don't know. |
|
Back to top |
|
 |
|