|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
Reset a Msg Expiry time in MQ 9.2.2.0 |
« View previous topic :: View next topic » |
Author |
Message
|
JosephGramig |
Posted: Wed Jul 28, 2021 9:28 am Post subject: Reset a Msg Expiry time in MQ 9.2.2.0 |
|
|
 Grand Master
Joined: 09 Feb 2006 Posts: 1244 Location: Gold Coast of Florida, USA
|
A friend said he read an article stating there was a new feature at MQ 9.2.2.0 where the Admin could change the expiry from -1 (never) to a value that does expire.
I suppose this can be done with the dmpmqmsg (qload replacement), but that will reload the messages and mess with the order (possibly).
Just checking to see if one of you saw and book marked that article (assuming it did exist).
Thx |
|
Back to top |
|
 |
hughson |
Posted: Wed Jul 28, 2021 11:05 am Post subject: |
|
|
 Padawan
Joined: 09 May 2013 Posts: 1959 Location: Bay of Plenty, New Zealand
|
|
Back to top |
|
 |
JosephGramig |
Posted: Fri Jul 30, 2021 5:47 am Post subject: |
|
|
 Grand Master
Joined: 09 Feb 2006 Posts: 1244 Location: Gold Coast of Florida, USA
|
@Morag
Thx very much. There were many Google hits and some indicate this was introduced at 8.0.0.6 (so it has been around for a long time).
I see a comment in the KC saying DEFBIND(NOTFIXED) might produce different expiry times depending on the XMITQ. Later there is a note to not set CAPEXPRY on SYSTEM.CLUSTER.* queues. This looks to be in conflict unless it is using the QC def.
Related but different question. If a QR or QA has CAPEXPRY set, can an XMITQ override that value if it also has it set at a lower value?
I would not think so as many queues will likely go through the XMITQ. |
|
Back to top |
|
 |
bruce2359 |
Posted: Fri Jul 30, 2021 6:51 am Post subject: |
|
|
 Poobah
Joined: 05 Jan 2008 Posts: 9469 Location: US: west coast, almost. Otherwise, enroute.
|
From https://www.ibm.com/docs/en/ibm-mq/9.1?topic=mqlong-enforcing-lower-expiration-times
Quote: |
If more than one object is used on the resolution path, for example, when a message is put to an alias or remote queue, then the lowest of all the CAPEXPRY values is used as the upper limit for message expiry. |
Let confusion reign. _________________ 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 |
|
 |
|
|
 |
|
Page 1 of 1 |
|
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
|
|
|
|