Applied to both versions MQSI 2.0.1 and MQSI 2.0.2:
If you specify an expiry value when putting a message to a queue, MQSI shows MQMD expiry value as the Expiry Timestamp, not the integer value. Any fix from IBM for this problem ?
Joined: 28 Jun 2001 Posts: 2453 Location: Los Angeles
From the manual:
The Expiry field in the MQMD is a special case:
– If it is set to -1 (unlimited) it is converted to an integer
– If it is not set to -1, it is converted to a TIMESTAMP
If you need it as an integer, then you can subtract the CreationTime property from the ExpirationTime property. But I'm not sure what the units will be at this point.
But, I did notice that the way this field is handled is inconsistent. It only appears to do the above convertion on the incoming message. If you explicitly set the MQMD.Expiry in a Compute node, then referencing it later appears to give an Integer.
Cheers,
_________________ Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum