OK, I was proven wrong or unclear.
In fact the bug was introduced somewhere in v4.2.2.x and the solution for
it (cleanup backupgroup) in v4.2.2.y + v5.1.1.z. For sure bug and fix for
it were not in same patch ,-)
But even in V4.2.2.0 there were numerous reports to this list for some
expiration problems. Were they caused by system object or not, was not
clear.

Zlatko Krastev
IT Consultant






Steve Roder <spr AT REXX.ACSU.BUFFALO DOT EDU>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
14.10.2002 21:03
Please respond to "ADSM: Dist Stor Manager"


        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        cleanup backupgroup


> you got it right - there is a problem with SystemObject expiration
> introduced in v4.2.2 and you have to run CLEANUP BACKUPGROUP to prevent
> enourmous high space usage in DB and storage pool. This applies if you
> have many W2k nodes backing up to TSM. It would last until you upgrade
to
> a version without the bug. It is expected in v4.2.3 the bug to be fixed.
> So without upgrade (in far future) to v5.1.x you still can apply v4.2.3
> (or later) maintenance.

The "Cleanup" command does not exist on 4.2.2.0.  Gee, I guess if it did,
then IBM would have introduced a bug, and the fix for it, in the same
release!  I don't think the bug came in 4.2.2.0.

Tivoli Storage Manager
Command Line Administrative Interface - Version 5, Release 1, Level 5.0
(C) Copyright IBM Corporation 1990, 2002 All Rights Reserved.

Session established with server MEMNOCH: AIX-RS/6000
  Server Version 4, Release 2, Level 2.0
  Server date/time: 10/14/02   13:47:04  Last access: 10/14/02   13:00:03


tsm: MEMNOCH>CLEANUP BACKUPGROUP
ANR2000E Unknown command - CLEANUP BACKUPGROUP.
ANS8001I Return code 2.


Steve Roder, University at Buffalo
HOD Service Coordinator
VM Systems Programmer
UNIX Systems Administrator (Solaris and AIX)
TSM/ADSM Administrator
(spr AT buffalo DOT edu | (716)645-3564)