| Author |
Message
|
| PeterPotkay |
 Posted: Tue Dec 30, 2014 6:46 am Post subject: MQ Expiry Value - How is this possible? |
 |
|
Poobah
Joined: 15 May 2001
Posts: 7723
|
The below is the top snippet of the message from MO71. MQ Explorer and BMTM also confirm this value.
| Code: |
[ 364 bytes] Message Descriptor (MQMD)
StrucId :'MD '
Version :2
Report :00000000
Message Type :8 (Datagram)
Expiry :2146624636
Feedback :0 (None)
MQEncoding :0x'222'
CCSID :819
Format :'MQSTR '
Priority :0
Persistence :1 (Persistent) |
The value is decrementing.
This app is producing lots of messages like this.
WMB and DataPower are forwarding it along, maintaining that value!
How is this possible?
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
 |
| McueMart |
| Posted: Tue Dec 30, 2014 6:58 am Post subject: |
|
|
Chevalier
Joined: 29 Nov 2011
Posts: 490
Location: UK...somewhere
|
| Looks like someone use Int Max instead of MQEI_UNLIMITED on the Expiry field? |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue Dec 30, 2014 7:00 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Expiry value on a message should decrement each time the message is moved. The expiry on a queue is just a default.
Unless, as McueMart says, the value is set to MQEI_UNLIMITED. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Tue Dec 30, 2014 1:16 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7723
|
Jeff,
Its not Unlimited, its a value in the trillions. Which is higher than the supposed max of 999,999,999.
tczielke was able to reproduce this.
| Quote: |
| I just did a quick test on 7.5.0.3 Linux x86 with an augmented amqsput program that uses a md.Expiry of x’7FFFFFFF’, and the PUT was successful. |
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| tczielke |
| Posted: Tue Dec 30, 2014 1:29 pm Post subject: |
|
|
Guardian
Joined: 08 Jul 2010
Posts: 943
Location: Illinois, USA
|
| One clarification. The max positive value for an MQLONG or signed 4 byte integer like Expiry is in the billions (not trillions) = 2,147,483,647 = x'7FFFFFFF'. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Tue Dec 30, 2014 1:54 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7723
|
| PeterPotkay wrote: |
Jeff,
Its not Unlimited, its a value in the trillions. Which is higher than the supposed max of 999,999,999.
tczielke was able to reproduce this.
| Quote: |
| I just did a quick test on 7.5.0.3 Linux x86 with an augmented amqsput program that uses a md.Expiry of x’7FFFFFFF’, and the PUT was successful. |
|
Duh. I can only count so high even if I take off both my mittens and socks.
Yes, 2146624636 is in the billions not trillions. Its over 1 billion more than the supposed limit of nine 9s described in the manuals. I opened a PMR and will report back.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| tczielke |
| Posted: Tue Dec 30, 2014 2:02 pm Post subject: |
|
|
Guardian
Joined: 08 Jul 2010
Posts: 943
Location: Illinois, USA
|
You would need a lot of fingers and toes to count that high 
As a historical side note, the UK used to call a US trillion as a billion, pre-1975. |
|
| Back to top |
|
|
| mvic |
| Posted: Tue Dec 30, 2014 2:11 pm Post subject: Re: MQ Expiry Value - How is this possible? |
|
|
Jedi
Joined: 09 Mar 2004
Posts: 2080
|
| PeterPotkay wrote: |
This app is producing lots of messages like this.
WMB and DataPower are forwarding it along, maintaining that value!
How is this possible? |
Ask your app people? |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Tue Dec 30, 2014 2:29 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9486
Location: US: west coast, almost. Otherwise, enroute.
|
| PeterPotkay wrote: |
| ...the supposed limit of nine 9s described in the manuals. I opened a PMR and will report back. |
The z/TFP MQ doc says that a value of zero will result in an r/c 2013 EXPIRY_ERROR. There is no reference to the (old) max limit of 999,999,999.
I recall seeing somewhere (but can't find it now) that an absolute GMT time value in expiry is supported. I'm still looking.
_________________
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 |
|
|
| fjb_saper |
| Posted: Tue Dec 30, 2014 3:57 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20768
Location: LI,NY
|
| PeterPotkay wrote: |
| PeterPotkay wrote: |
Jeff,
Its not Unlimited, its a value in the trillions. Which is higher than the supposed max of 999,999,999.
tczielke was able to reproduce this.
| Quote: |
| I just did a quick test on 7.5.0.3 Linux x86 with an augmented amqsput program that uses a md.Expiry of x’7FFFFFFF’, and the PUT was successful. |
|
Duh. I can only count so high even if I take off both my mittens and socks.
Yes, 2146624636 is in the billions not trillions. Its over 1 billion more than the supposed limit of nine 9s described in the manuals. I opened a PMR and will report back. |
Duh isn't the expiry unlimitted x'FFFFFFFF' ? as in -1 ?? So what Tczielke tried was just the highest positive value... for the size of the DWord and by the way 999,999,999 translates to x'3B9AC9FF'
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Tue Dec 30, 2014 3:58 pm Post subject: Re: MQ Expiry Value - How is this possible? |
|
|
Poobah
Joined: 15 May 2001
Posts: 7723
|
| mvic wrote: |
| PeterPotkay wrote: |
This app is producing lots of messages like this.
WMB and DataPower are forwarding it along, maintaining that value!
How is this possible? |
Ask your app people? |
No matter what they say or show me, the question remains. The manuals say 999999999 is the max value.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Dec 30, 2014 4:03 pm Post subject: Re: MQ Expiry Value - How is this possible? |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20768
Location: LI,NY
|
| PeterPotkay wrote: |
| mvic wrote: |
| PeterPotkay wrote: |
This app is producing lots of messages like this.
WMB and DataPower are forwarding it along, maintaining that value!
How is this possible? |
Ask your app people? |
No matter what they say or show me, the question remains. The manuals say 999999999 is the max value. |
Probably because 2,147,483,647 is less speaking to the mind (7FFF FFFF)... or because you cannot parse more than that value (max string length allowed for parsing) 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| tczielke |
| Posted: Tue Dec 30, 2014 6:01 pm Post subject: |
|
|
Guardian
Joined: 08 Jul 2010
Posts: 943
Location: Illinois, USA
|
| The MQ manual is good, but it does have flaws. I am writing a PCF application and following the manual, and have found at least 10+ errors in it, so far. The 999,999,999 is probably wrong, but a PMR makes the most sense to get an answer from the horse's mouth. |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Tue Dec 30, 2014 10:35 pm Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
| tczielke wrote: |
| I am writing a PCF application and following the manual, and have found at least 10+ errors in it, so far. |
You are being a good citizen and passing those errors back to IBM aren't you?
If you are not then now is a good time to make it you new years resolution.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| tczielke |
| Posted: Wed Dec 31, 2014 5:15 am Post subject: |
|
|
Guardian
Joined: 08 Jul 2010
Posts: 943
Location: Illinois, USA
|
| I was good about reporting manual errors with the Infocenter. However, with the Knowledge Center, it has either not worked or given me bizarre results when I have tried, so at this point I have stopped with the KC. |
|
| Back to top |
|
|
|
|
