I don't know how indexing would effect this. Since all of our mainframe queues are at or near zero when things are working properly, we never bothered with indexing. I would guess some message would not be touched in this scenario like you said.
Peter Potkay IBM MQSeries Certified Specialist, Developer [EMAIL PROTECTED] X 77906 -----Original Message----- From: Bullock, Rebecca (CSC) [mailto:[EMAIL PROTECTED]] Sent: Tuesday, August 27, 2002 8:15 AM To: [EMAIL PROTECTED] Subject: Re: Expiration time problem. Peter, is this true even if the queue is indexed based on msgid or correlid? In that case, there'd be no need to start at the top and work your way down, so some expired messages wouldn't be touched. For me, it's a moot point since I'm running V5.2 and Tom S. says that the browse will do to delete expired messages. Tom Schneider: Thanks. We are running V5.2 on OS/390. I'll try out the browse -- Rebecca -----Original Message----- From: Potkay, Peter M (PLC, IT) [mailto:[EMAIL PROTECTED]] Sent: Tuesday, August 27, 2002 7:10 AM To: [EMAIL PROTECTED] Subject: Re: Expiration time problem. Rebecca, If your app is getting by MessageID or CorrelId and is doing a destructive get, MQ starts at the top of the queue and works its way down till it finds yours. As it goes top to bottom, it "touches" each message to see if it matches your selection criteria. If it does, you get it. If it doesn't, its left alone. If its expired, goodbye expired message. We rely on this behavior in production and all our queues are free of expired messages. Peter Potkay IBM MQSeries Certified Specialist, Developer [EMAIL PROTECTED] X 77906 -----Original Message----- From: Bullock, Rebecca (CSC) [mailto:[EMAIL PROTECTED]] Sent: Monday, August 26, 2002 4:28 PM To: [EMAIL PROTECTED] Subject: Re: Expiration time problem. Pablo, this is normal. Expired messages will stay on the queue until they are read (or until you try to read them). 1) For nonOS/390, a browse will do it. Just browse all the messages in the queue. 2) For OS/390, the read must be a destructive one. This raises the interesting question of how you get rid of expired messages but leave nonexpired ones alone if your applications don't just read everything on the queue (if, for example, you get by msgid or correlid). I don't have an answer to that. Does anyone out there? Best regards, Rebecca Rebecca Bullock Computer Sciences Corporation Educational Testing Service Account Princeton, NJ 08541 e-mail: [EMAIL PROTECTED][EMAIL PROTECTED] -----Original Message----- From: Pablo Javier Carreras [mailto:[EMAIL PROTECTED]] Sent: Monday, August 26, 2002 4:36 PM To: [EMAIL PROTECTED] Subject: Expiration time problem. Hi all, An on-line application puts messages on a queue with the expiration time option. And after this time is over, although there are no messages on the queue, I can still see (by executing a DIS QUEUE command) that the curdepth of the queue is 1983 and not 0. Is this a normal behaviour when expiration time is used? Can anybody tell me when this depth value is goning to be refreshed? Thanks in advance. Pablo. -- Pablo Javier Carreras Gerencia de Infraestructura Tecnol�gica - Area Mainframe Banco RIO de la Plata S.A. - Grupo SCH Bartolom� Mitre 480 - 2do. piso Buenos Aires - Argentina Tel. (54)11-4341-1000 Int. 3596 Fax. (54)11-4341-1620 ************************************************************************ Visite http://www.bancorio.com.ar y tenga el Banco al alcance de su mano. ************************************************************************ NOTA DE CONFIDENCIALIDAD / CONFIDENTIALITY NOTE Este mensaje (y sus anexos) es confidencial y puede contener informacion (i) de propiedad exclusiva de Banco Rio de la Plata S.A. sus afiliadas o subsidiarias; o (ii) amparada por el secreto profesional. Si usted ha recibido este fax o e-mail por error, por favor comuniquelo inmediatamente via fax o e-mail y tenga la amabilidad de destruirlo; no debera copiar el mensaje ni divulgar su contenido a ninguna persona. Muchas gracias. This message (including attachments) is confidential. It may also contain information that (i) is exclusively property of Banco Rio de la Plata S.A. or its affiliates or subsidiaries; or (ii) is privileged or otherwise legally exempt from disclosure. If you have received it by mistake please let us know by fax or e-mail immediately and destroy or delete it from your files or system; you should also not copy the message nor disclose its contents to anyone. Thank you. ************************************************************************** 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 ************************************************************************** This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited. Thank you for your compliance. 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 This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential or privileged information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return email and delete this communication and destroy all copies. 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 ************************************************************************** This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited. Thank you for your compliance. 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
