I'm a newcomer to this list, and a newcomer to TSM. So there's a very good chance that I'm totally confused. I'm catching the tail end of this cleanup backupgroups discussion, and I need some clarification.
I think I'm reading that there's a problem in 4.2.2.x versions of TSM which causes SYSTEM OBJECTS not to expire, requiring the CLEANUP BACKUPGROUPS. I've seen some messages that indicate the cleanup needs to run after conversion to 5.1. We're running TSM 4.2.2.0 on Solaris. We hope to upgrade to 5.1 sometime, but probably not soon. While we're still on 4.2.2.0, do we need to do this cleanup regularly? We recently had a problem with TSM coming to a screeching halt after our database got 100% full, and we're not sure why a database that was supposedly way bigger than we would ever need has filled up before we've even got half our backups on it. Is it possible that this systems objects problem is contributing to our db size problem? -- Matt Simpson -- OS/390 Support 219 McVey Hall -- (859) 257-2900 x300 University Of Kentucky, Lexington, KY 40506 <mailto:[EMAIL PROTECTED]> mainframe -- An obsolete device still used by thousands of obsolete companies serving billions of obsolete customers and making huge obsolete profits for their obsolete shareholders. And this year's run twice as fast as last year's.
