Re: Getting rid of expired messages
If I remember correctly, one destructive get for a msgid/correlid combination that cannot exist will purge all expired messages. -Original Message- From: Jeff A Tressler [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 12, 2004 11:06 AM To: [EMAIL PROTECTED] Subject: Getting rid of expired messages Two questions 1) "If you are using V5.3 a browse will remove the expired messages." >From the Reason Code 2033 thread. I thought browse would work on any version. We use MQSeries v5.1 for HP-UX 11.x. If browse does not work how do we clean up unexpired messages? Doing a destructive read and putting the unexpired messages back seems extreme. 2) Sending system send bunch of messages with expiration. The destination system is down so messages back up in transmission queue and expiration time is exceeded. When the destination is back on-line, does the MCA remove the expired messages or does it pass them down the channel. I expect the MCA, doing a destructive read, will result in the expired messages being deleted. Jeff Tressler Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: Getting rid of expired messages
Jeff, I probably didn't say that quite right. The difference when you are browsing with 5.3 - the message is physically deleted, just like when you were doing the destructive get. In any case an expired message should NEVER be returned to your application. Gregg -Original Message- From: Jeff A Tressler [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 12, 2004 1:45 PM To: [EMAIL PROTECTED] Subject: Re: Getting rid of expired messages When an application attempts read a expired message using a destructive MQGET on any version, the result is the same as if that message does not exist. it doesn't matter if the application in the Channel initiator, MQ or you. The difference with 5.3 is that the result is the same when browsing. Gregg Tuben Lead Developer z/OS WSMQ products BMC Software Inc. === Ok I realized I left something out. We will be reading by Correl ID and in this case, we will not be doing destructive reads on the expired messages during normal application processing. The application will know the message expired and will not keep trying to read the message once it times out. Thus we need a background process to do the clean up. Having the background process do a destructive read and then put the messages successfully read seems excessive. I was under the impression that doing a BROWSE in v5.1 would accomplish the deletion. Jeff Tressler Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: Getting rid of expired messages
When an application attempts read a expired message using a destructive MQGET on any version, the result is the same as if that message does not exist. it doesn't matter if the application in the Channel initiator, MQ or you. The difference with 5.3 is that the result is the same when browsing. Gregg Tuben Lead Developer z/OS WSMQ products BMC Software Inc. === Ok I realized I left something out. We will be reading by Correl ID and in this case, we will not be doing destructive reads on the expired messages during normal application processing. The application will know the message expired and will not keep trying to read the message once it times out. Thus we need a background process to do the clean up. Having the background process do a destructive read and then put the messages successfully read seems excessive. I was under the impression that doing a BROWSE in v5.1 would accomplish the deletion. Jeff Tressler Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: Getting rid of expired messages
When an application attempts read a expired message using a destructive MQGET on any version, the result is the same as if that message does not exist. it doesn't matter if the application in the Channel initiator, MQ or you. The difference with 5.3 is that the result is the same when browsing. Gregg Tuben Lead Developer z/OS WSMQ products BMC Software Inc. -Original Message- From: Jeff A Tressler [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 12, 2004 1:06 PM To: [EMAIL PROTECTED] Subject: Getting rid of expired messages Two questions 1) "If you are using V5.3 a browse will remove the expired messages." >From the Reason Code 2033 thread. I thought browse would work on any version. We use MQSeries v5.1 for HP-UX 11.x. If browse does not work how do we clean up unexpired messages? Doing a destructive read and putting the unexpired messages back seems extreme. 2) Sending system send bunch of messages with expiration. The destination system is down so messages back up in transmission queue and expiration time is exceeded. When the destination is back on-line, does the MCA remove the expired messages or does it pass them down the channel. I expect the MCA, doing a destructive read, will result in the expired messages being deleted. Jeff Tressler Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Getting rid of expired messages
Two questions 1) "If you are using V5.3 a browse will remove the expired messages." >From the Reason Code 2033 thread. I thought browse would work on any version. We use MQSeries v5.1 for HP-UX 11.x. If browse does not work how do we clean up unexpired messages? Doing a destructive read and putting the unexpired messages back seems extreme. 2) Sending system send bunch of messages with expiration. The destination system is down so messages back up in transmission queue and expiration time is exceeded. When the destination is back on-line, does the MCA remove the expired messages or does it pass them down the channel. I expect the MCA, doing a destructive read, will result in the expired messages being deleted. Jeff Tressler Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
