Curtis,

Try setting summaryretention to 1, stop the server, change system date to 2
days later than the bad date, start dsmserv, ACCEPT DATE -- all of this with
sessions and schedules disabled, to prevent further records;  after purge
processing, stop the server, reset system date, start dsmserv, set retention
to desired interval, maybe 30 --- did you already do an ACCEPT DATE cmd
(after the accidental time-source problem)?

This sounds like you need a debug command to clear up;  did you get any help
from TSM Support folks?  I'd guess other folks have this problem, but might
not notice until they run an open-ended date on their query (like TDS does).

Regards,
Don

Don France
Technical Architect - Tivoli Storage Manager
Professional Association of Contract Employees (P.A.C.E.)
San Jose, CA (408) 257-3037
don_france AT att DOT net