Re: Read: Expryint

2004-07-21 Thread Miller, Dennis
Title: Message



He's 
Ba-aack! 

  
  -Original Message-From: emque5 
  [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 20, 2004 4:32 
  PMTo: [EMAIL PROTECTED]Subject: Read: 
  Expryint
  Your message    To:  
  [EMAIL PROTECTED]    Subject:  Re: 
  Expryint    Sent:  8/07/2004 6:03 a.m.was read 
  on 21/07/2004 11:30 a.m.. 


Re: Read: Expryint

2004-07-21 Thread Anthony G Allison

Look emque5. 

We are getting very tired of your read replies to every message in the board.  Nobody on this board cares if you read your messages or not. PLEASE TURN THIS OFF!




Anthony Allison
Senior Systems / Middleware Engineer
CSC 
1001 G Street
Suite 800
WDC, 20001
(202) 824-7938
[EMAIL PROTECTED]



This is a PRIVATE message. If you are not the intended recipient, please delete without copying and kindly advise us by e-mail of the mistake in delivery. NOTE: Regardless of content, this e-mail shall not operate to bind CSC to any order or other contract unless pursuant to explicit written agreement or government initiative expressly permitting the use of e-mail for such purpose.








emque5 
@HOTMAIL.COM>
Sent by: MQSeries List 
07/20/2004 07:31 PM
Please respond to MQSeries List

        
        To:        [EMAIL PROTECTED]
        cc:        
        Subject:        Read: Expryint


Your message

    To:  [EMAIL PROTECTED]
    Subject:  Re: Expryint
    Sent:  8/07/2004 6:03 a.m.

was read on 21/07/2004 11:30 a.m.. Reporting-UA: pcgirish; Microsoft Office Outlook, Build 11.0.5510
Final-Recipient: rfc822;[EMAIL PROTECTED]
Original-Message-ID:  <[EMAIL PROTECTED]>
Disposition: manual-action/MDN-sent-automatically; displayed




Read: Expryint

2004-07-20 Thread emque5
Title: Read: Expryint






Your message

    To:  [EMAIL PROTECTED]
    Subject:  Expryint
    Sent:  8/07/2004 3:46 a.m.

was read on 21/07/2004 11:32 a.m..





binQj9vem0zgQ.bin
Description: message/disposition-notification


Read: Expryint

2004-07-20 Thread emque5
Title: Read: Expryint






Your message

    To:  [EMAIL PROTECTED]
    Subject:  Re: Expryint
    Sent:  8/07/2004 6:03 a.m.

was read on 21/07/2004 11:30 a.m..





binpOoS28eGil.bin
Description: message/disposition-notification


Re: Expryint

2004-07-07 Thread Bruce Giordano

You can run the command: REFRESH QMGR TYPE(EXPIRY) NAME(YOUR.QUEUE.NAME) in
order to have an individual queue scanned for expired messages.  You could
also have a group of queues scanned by specifying a wildcard in the name.
- Bruce Giordano



  "Williams, Dave (Systems
  Management)" <[EMAIL PROTECTED]>   To:   
  [EMAIL PROTECTED]
  cc:
  Sent by: MQSeries List  Subject:   Expryint
  <[EMAIL PROTECTED]>



  Wednesday July 7, 2004 11:46 AM
  Please respond to MQSeries List







The queue manager can periodically scan individual queues, or all queues
belonging to a particular queue manager, for expired messages, which are
then deleted. You can choose how often this scanning should take place,
if at all, or you can define it so that the queue manager automatically
calculates when the expired messages should be scanned and deleted. The
EXPRYINT queue manager attribute controls this. This is from the manual.
How do we specify an individual queue to be scanned?
Thanks,

 Dave
(See attached file: C.htm)


Title: Expryint







The queue manager can periodically scan individual queues, or all queues belonging to a particular queue manager, for expired messages, which are then deleted. You can choose how often this scanning should take place, if at all, or you can define it so that the queue manager automatically calculates when the expired messages should be scanned and deleted. The EXPRYINT queue manager attribute controls this. This is from the manual. How do we specify an individual queue to be scanned? 

Thanks, 

Dave




Expryint

2004-07-07 Thread Williams, Dave (Systems Management)
Title: Expryint







The queue manager can periodically scan individual queues, or all queues belonging to a particular queue manager, for expired messages, which are then deleted. You can choose how often this scanning should take place, if at all, or you can define it so that the queue manager automatically calculates when the expired messages should be scanned and deleted. The EXPRYINT queue manager attribute controls this. This is from the manual. How do we specify an individual queue to be scanned? 

Thanks, 

Dave




Re: removal of expired messages in 5.3 (EXPRYINT)

2003-01-13 Thread Jan van Kemenade
Hi,

> Bruce is this feature available on 5.2 ?

No, this is new in 5.3 . You can also issue a REFRESH QMGR with the
EXPIRE keyword, I believe.

Cheers, Jan.
>
>
>
>

-/
/&Jan van Kemenade
\&www.cressida.info
-\

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