| Author |
Message
|
| mountisland |
 Posted: Fri Sep 14, 2007 3:47 am Post subject: MQMD.Format=MQSTR |
 |
|
Newbie
Joined: 14 Sep 2007
Posts: 3
|
| Is there a way of setting a config file for MQSeries with MQMD.Format=MQSTR so that messages being sent to a remote system are received as text only? Is there any property setting on MQSeries that can be set? I am using V5.3 and V6.0 |
|
| Back to top |
|
 |
| AkankshA |
| Posted: Fri Sep 14, 2007 3:50 am Post subject: |
|
|
Grand Master
Joined: 12 Jan 2006
Posts: 1494
Location: Singapore
|
i am sorry but i am not completely clear...
you want to set MQMD.Format field to MQSTR.... set it for messages while sending or when you are adding up MQMD header to send on a queue..
did i miss something.. or i misunderstood something... 
_________________
Cheers |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Fri Sep 14, 2007 3:50 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Format is always set on individual messages, by the program that is putting the messages.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| zpat |
| Posted: Sun Sep 16, 2007 11:20 pm Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
If you mean change the default message format from NONE to STRING, that would be very useful, but not possible.
Getting the application changed would probably be easiest, but coding an API exit (to set the format) is another possibility. |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Sep 17, 2007 12:14 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
I add the standard warning about exits, advanced topic, can cause serious problems, here be monsters, etc, etc.
Doing a search on exits will give you greater detail on this. Change the application to set the format - easier & safer.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Nigelg |
| Posted: Mon Sep 17, 2007 12:26 am Post subject: |
|
|
Grand Master
Joined: 02 Aug 2004
Posts: 1046
|
| Quote: |
If you mean change the default message format from NONE to STRING, that would be very useful, but not possible.
|
It is possible to change the default msg format; edit cmqc.h and change the value in the macro definition of MQMD_DEFAULT. You will need to remember to change the definition again after applying maintenance.
_________________
MQSeries.net helps those who help themselves.. |
|
| Back to top |
|
|
| zpat |
| Posted: Mon Sep 17, 2007 2:57 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
That would only work for applications written in-house in C language and re-compiled.
The problem usually arises when applications come from outside or have been working on one platform without problems and need to work over different platforms.
Also a lot of applications are not written in C, even if the lower level interface to the MQI might be.
It can be hard to get source re-compiled, in fact it might be as easy to have it changed to explicitly code the format. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Mon Sep 17, 2007 3:12 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| zpat wrote: |
| That would only work for applications written in-house in C language and re-compiled. |
That also used MQMD_DEFAULT.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Nigelg |
| Posted: Mon Sep 17, 2007 4:56 am Post subject: |
|
|
Grand Master
Joined: 02 Aug 2004
Posts: 1046
|
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Sep 17, 2007 5:09 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Nigelg wrote: |
So we have decided that the best thing to do is to make app writers take responsibility for specifying the msg format themselves rather than relying on a default.
|
Absolutely. I still stand by my thought that the default value should be "FORMAT_AS_QMGR_DEFAULT" but until IBM develop that we're kinda stuck. With all the issues discussed in the other thread. Except that developers seem to be getting recruited on smaller budgets these days.
Before everyone jumps on me, I accept that development of such an option would still require rework in the existing application code base but at least it's a fairly simple edit/replace/recompile. Which doesn't obviate the need for all the code to go through a testing cycle at enormous cost. The reason, I suspect, it's not being pushed hard by the customer base.
Be nice to have it in the back pocket for new developments though.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Mon Sep 17, 2007 5:45 am Post subject: |
|
|
Guest
|
| Quote: |
Nigelg wrote:
So we have decided that the best thing to do is to make app writers take responsibility for specifying the msg format themselves rather than relying on a default. |
Allow me to pick a nit:
Fields in the MD, and other MQ structures, have Initial Values, not defaults.
It is the responsibility of the application developer to change the values of these fields to meet application requirements. This is the same responsibility developers have with the application data. |
|
| Back to top |
|
|
|
|
