I have seen this problem on the NT platform running the 3.7.2 code. It appears
to only happen when another process, usually, reclamation, is also running. I
now run the expiration job twice a day, around 7:00 AM and again around 12:00
noon. Under normal circumstances, I don't have any other jobs running during
these times, and the expiration runs fine.

Mike Wiederkehr
3M Austin Center





Brian Johnson <bjohnson AT AFCE DOT COM> on 04/19/2000 08:26:14 AM

Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>

To:   ADSM-L AT VM.MARIST DOT EDU
cc:    (bcc: Mike H. Wiederkehr/AT-Austin/3M/US)
Subject:  Expiration not working



Hello all,

Has anyone else had the same problems as below: -

We have a TSM Server (3.7.2.0) on an AIX 4.3.2 RS/6000 box. Expire inventory has
started acting very strangely,

at 08:00 a few days ago  a daily  Admin schedule started expire inv

 1,212     Expiration               Examined 5 objects, deleting 0 backup
objects, 0
                                       archive objects, 0 DB backup volumes, 0
recovery
                                       plan files; 0 errors encountered.



at 09:00 the q proc produced: -

 1,212     Expiration               Examined 5 objects, deleting 0 backup
objects, 0
                                       archive objects, 0 DB backup volumes, 0
recovery
                                       plan files; 0 errors encountered.


Then at 16:00

 1,212     Expiration               Examined 2306 objects, deleting 0 backup
objects, 256
                                       archive objects, 0 DB backup volumes, 0
recovery
                                       plan files; 0 errors encountered.


This has happened for about a week now - Expire inv running very slow and NOT
expiring any backup objects - when we know there should be thousands being
expired, any ideas???

Thanks in advance,

Brian Johnson