>     If I don't run expiration DAILY I'm in a world of HURT !
>
>     (well, consumption of 3590 tapes is about 150 per day... I would have
>     to add 1 3494-S10 every two days)
>
>     Dwight
>
>     Oh, any word on 3.1.2.31 ?
>
>
>______________________________ Reply Separator
_________________________________
>Subject: Re: WARNING, READ THIS BEFORE INSTALLING the ADSM server 3
>Author:  g.rentschler (g.rentschler AT RUS.UNI-STUTTGART DOT DE) at unix,mime
>Date:    7/20/99 2:20 AM
>
>
>Hello Tom,
>do you want to say that expiration shouldn't be run at all? I think
>most sites do not run expiration automatically using the expinterval
>option but via cronjob or admin schedule.
>Furthermore, not running expiration for some time is a problem for many
>large sites. It may cause the DB and tape usage to grow dramatically.
>After the problem is solved the the epxpiration will take a long time.
>
>Should we better go back to 3.1.2.20?
>Best regards
>Gerhard
>
>---
>Gerhard Rentschler            email:g.rentschler AT rus.uni-stuttgart DOT de
>Regional Computing Center     tel.   ++49/711/685 5806
>University of Stuttgart       fax:   ++49/711/682357
>Allmandring 30a
>D 70550
>Stuttgart
>Germany
>
>
>-----Original Message-----
>From:   Tom Brooks [SMTP:tbrooks AT VNET.IBM DOT COM]
>Sent:   Monday, July 19, 1999 11:43 PM
>To:     ADSM-L AT VM.MARIST DOT EDU
>Subject:        WARNING, READ THIS BEFORE INSTALLING the ADSM server
3.1.2.30
>
>[Gerhard Rentschler]  Some lines deleted.....
>
>IF YOU HAVE ALREADY APPLIED 3.1.2.30 and you are exposed
>
>1) Halt the server
>2) Set the server option EXPINTERVAL 0 (in the server options file).
>3) Re-Start the server
>
>We are working to correct this as soon as possible
>
>Tom Brooks
>ADSM Server APAR Coordinator
>ADSM Server Development