Setting message properties

[Dariusz Suchojad]

It has been reported in a private e-mail that PyMQI (as of version 1.2) is missing pretty much everything that's need for setting of and querying by custom MQ 7.0-style message properties. These IBM presentations give a good overview of what can be implemented http://j.mp/hmoD2V http://j.mp/gQ2jHk This includes supporting new MQ verbs, such as MQCMHO, MQCRTMH, MQINQMP etc.

[Dariusz Suchojad (dsuch)]

So I'm implementing MQSETMP right now and wonder what the default data type should be. I guess string will do, no? Most of the message properties will be strings not some fancy MQTYPE_FLOAT32 and that's what we should default to? What to do you think?

[Phil Denton (pdenton)]

I think that makes sense in general. For our needs specifically, I
think we’ll be using all (or nearly all) strings. However, assuming
“value” is a kwarg in pymqi, I would assume the default value should
be None and the default type should be MQTYPE_NULL.

Phil

On Wed, Apr 27, 2011 at 3:19 PM, Dariusz Suchojad
<email address hidden> wrote:
> So I'm implementing MQSETMP right now and wonder what the default data
> type should be. I guess string will do, no? Most of the message
> properties will be strings not some fancy MQTYPE_FLOAT32 and that's what
> we should default to? What to do you think?
>
> --
> You received this bug notification because you are a direct subscriber
> of the bug.
> https://bugs.launchpad.net/bugs/755004
>
> Title:
>  Setting message properties
>
> Status in Python interface to WebSphere MQ:
>  Confirmed
>
> Bug description:
>  It has been reported in a private e-mail that PyMQI (as of version
>  1.2) is missing pretty much everything that's need for setting of and
>  querying by custom MQ 7.0-style message properties. These IBM
>  presentations give a good overview of what can be implemented
>  http://j.mp/hmoD2V http://j.mp/gQ2jHk This includes supporting new MQ
>  verbs, such as MQCMHO, MQCRTMH, MQINQMP etc.
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/pymqi/+bug/755004/+subscribe
>

[Dariusz Suchojad (dsuch)]

OK, I'm working on MQINQMP right now and need some hint regarding the default length of the buffer for fetching string properties. This will be customizable of course but I need to settle on something and have chosen the value of 64 characters. By default that many bytes will be allocated on each call to fetch a string property. If it's not enough an exception will be raised and its details will contain information how many bytes there need to be so that an application can re-issue the call with the new value for the buffer's length. What do you think of that 64 bytes thing?

[Phil Denton (pdenton)]

Yeah that should work for us. We will definitely have some properties
longer than 64 bytes but we'll be able to specify their length. Would
it be possible for pymqi to use MQIMPO_QUERY_LENGTH to handle that by
default as well the ability to specify? I'm not sure if that's the
proper use of that value but it seems like it could avoid any
exceptions. If that's not possible or doesn't make sense, your
solution should work fine as well.

Thanks,
Phil

On Thu, Apr 28, 2011 at 5:51 AM, Dariusz Suchojad
<email address hidden> wrote:
> OK, I'm working on MQINQMP right now and need some hint regarding the
> default length of the buffer for fetching string properties. This will
> be customizable of course but I need to settle on something and have
> chosen the value of 64 characters. By default that many bytes will be
> allocated on each call to fetch a string property. If it's not enough an
> exception will be raised and its details will contain information how
> many bytes there need to be so that an application can re-issue the call
> with the new value for the buffer's length. What do you think of that 64
> bytes thing?
>
> --
> You received this bug notification because you are a direct subscriber
> of the bug.
> https://bugs.launchpad.net/bugs/755004
>
> Title:
>  Setting message properties
>
> Status in Python interface to WebSphere MQ:
>  Confirmed
>
> Bug description:
>  It has been reported in a private e-mail that PyMQI (as of version
>  1.2) is missing pretty much everything that's need for setting of and
>  querying by custom MQ 7.0-style message properties. These IBM
>  presentations give a good overview of what can be implemented
>  http://j.mp/hmoD2V http://j.mp/gQ2jHk This includes supporting new MQ
>  verbs, such as MQCMHO, MQCRTMH, MQINQMP etc.
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/pymqi/+bug/755004/+subscribe
>

[Dariusz Suchojad (dsuch)]

Fix merged into trunk in r63 http://bazaar.launchpad.net/~dsuch/pymqi/trunk/revision/63

[Dariusz Suchojad (dsuch)]

I've just released PyMQI 1.3 and the development effort has moved to GitHub - https://github.com/dsuch/pymqi