The expired file remains in the ADSM database until an 'expire inventroy'
command is run.  The expiration interval (EXPInterval) is set in
the dsmserv.opt file.  I have set mine to 0 and use an administrative
schedule to issue the command.  That way I control the start time.

On Wed, 3 Mar 1999, Cohn, Grant wrote:

> Greetings all
>
> Can anyone tell me what is actually happening to a file when it is expired?
> Is it being marked as inactive or is it actually being deleted from the ADSM
> database?
>
> I see the following in the dsmsched.log file :
>
> 03/02/1999 21:25:39 Expiring-->                  0
> I:\Common\Utilops\fsa11.tmp  Sent
> 03/02/1999 21:25:39 Expiring-->                  0
> I:\Common\Utilops\fsa7.tmp  Sent
> 03/02/1999 21:25:39 Expiring-->                  0
> I:\Common\Utilops\fsa8.tmp  Sent
>
>
> We are running ADSM NT Client V2.1
> and ADSM Server 2.1.5.15
>
> Many thanks
>
>
> Grant Cohn
>
> Shell & BP South African Petroleum Refineries
> Durban, South Africa.
> Tel     :   (+27)  (0)31 - 480 1610
> Cell    :   (+27)  (0)83 254 4012
> e-mail :   grant .cohn AT sapref DOT com
>