Drats... we're about to upgrade to 5.1.1.6 (from 4.2.2.12, if only to get
past this issue);  but, it sounds like you ran okay -- are you saying
expiration & cleanup ran, but failed to "clean" out the old SysObj's from
the database?!?

Let us know, eh?


Don France
Technical Architect -- Tivoli Certified Consultant
Tivoli Storage Manager, WinNT/2K, AIX/Unix, OS/390
San Jose, Ca
(408) 257-3037
mailto:don_france AT att DOT net

Professional Association of Contract Employees
(P.A.C.E. -- www.pacepros.com)



-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
Gretchen L. Thiele
Sent: Tuesday, October 15, 2002 8:11 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: SYSTEM OBJECT problem back in v5.1.5.1?


I've just put v5.1.5.1 into test and it looks like the SYSTEM OBJECT
problem (failure to expire the elements in the SYSTEM OBJECT filespace
for Win2K and WinXP) is back. Has anyone else seen this?

My test server: Solaris 2.8, TSM v5.1.5.1
Clients: WinXP, TSM v5.1.1.0 and Win2K, TSM v4.2.1.0

I ran the expiration successfully and to completion as well as
the cleanup backupgroups command.

Will check this out on AIX 4.3.3, TSM v5.1.5.1 this afternoon.

Gretchen Thiele
Princeton University