See my comments inline.  You can search www.adsm.org for messages on this
subject.  Use the keyword "CLEANUP".

Paul D. Seay, Jr.
Technical Specialist
Naptheon Inc.
757-688-8180


-----Original Message-----
From: Matt Simpson [mailto:msimpson AT UKY DOT EDU]
Sent: Thursday, October 17, 2002 4:33 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Cleanup Backgroups and upgrade 4.2.2.0 to ??


I'm still trying to piece together all the snippets of information I've
gathered here to try to figure out what our plan of action should be.

We're running TSM Server 4.2.2.0 on Solaris.  General consensus seems to be
that 4.2.2.0 is not a good place to be.

We have Windows clients, so i assume there's a good probability that we have
the problem with orphan system objects that has been described here.  Our
database has grown larger faster than we expected, but I don't know if
that's due to the system objects problem or just normal growth.

At 4.2.2.0, we don't have the Cleanup Backupgroups function.

Should we go to 4.2.3? Or 5.1.something?
** The latest recommendation I have heard from support is to do the cleanup
backupgroups first.  4.2.3 supposedly requires an upgrade db.  I cannot say
go to that release so quickly, but there is still one bug in the 4.2.2.13
cleanup backupgroups function that most customers hit.

I think I read something here indicating that upgrading a DB to 5.1 might
fail unless the Cleanup was run first. but I haven't been able to find that
message again in the archives.

Do we have to go to 4.2.3 so we can do a cleanup before going to 5.1.?  Or
can we go straight to 5.1.? and then run the Cleanup?
** Gretchen has published some of the pain of doing this, but 5.1.5.1 may be
good enough.  Gretchen thinks not.  She believes problems have been
reintroduced.  What we did was got a special patch to 4.2.2.13, ran that for
just the cleanup backup groups when we hit the error condition that showed
on 4.2.2.12 and then reverted back to 4.2.2.12 only because we run Storage
Agents and they must match on release down to the patch level now.

I also saw a message suggesting that maybe the system objects bug had
returned in 5.1.5.1, but haven't seen any more discussion about that.
** Gretchen will come up for air at some point and let us know.

Any advice or horror stories would be muchly appreciated.
The longer you wait the worse the problem gets.
--


Matt Simpson --  OS/390 Support
219 McVey Hall  -- (859) 257-2900 x300
University Of Kentucky, Lexington, KY 40506 <mailto:msimpson AT uky DOT edu>
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.