Robert - Both TSM Tech Support and a local consultant recommended that we run the 'cleanup backupgroups' utility before we moved up to 5.2 (btw, mine is a z/OS shop and we recently moved from 5.1.9 to 5.2.3). This utility cleans up orphaned database objects, which will extend your upgradedb run significantly if not cleaned up. My understanding is that the utility only became available with 5.1.73. So, we upgraded from 5.1.65 to 5.1.9 back in June in preparation for the recent upgrade. Then, a few weeks ago, we went to 5.2.3.
Incidentally, the upgrade from 5.1.9 to 5.2.3 took quite a while for us - about 11 hours, because of the UPGRADEDB parameter. My TSM DB is about 23 GB. Other TSM Admins have reported quicker upgrade rates, so your time may very well be better. But, as a word of warning, allow a fairly large upgrade window, so you don't have to restore to your previous version - like I did the first time I attempted it. Good luck, Dave. -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Klein, Robert (NIH/CIT) Sent: Monday, October 18, 2004 9:27 AM To: [EMAIL PROTECTED] Subject: Migrating to TSM V5.2 on z?OS Believe it or not, we are still running TSM V4.2.2 on OS/390. We are planning to upgrade our OS to z/OS and, along with that, to upgrade to TSM V5.2. I have heard that on some other platforms (e.g. AIX) one cannot go directly from 4.2.2 to V5x. I don't see anything about such a restriction in the V5.2 for z/OS Quick Start manual, but wanted to check whether anyone was aware of this issue for migration to 5.2 on z/OS. Thanks for any input.
