Charles,
   Your comment is good because IBM recommends us to go to AIX 5.1.7 first
because of the window clients.  We have a small number of window clients,
less than 10.  Have you ever done a restore of the TSM database?   I like
to have this info in case I have to back out the migration.
    I was told that IBM no longer support upgrade questions.  The service
ended this October.
Any notes from your upgrade would be appreciated.
                                                       Thanks,
Helen

At 01:15 PM 12/18/2003 -0600, you wrote:

We recently went from 4.1.6 to 5.1.7.  The readme in 5.1.7 stated there
were significant upgrade db perf in 5.1.7 and if you are upgrading from
4.x go to 5.1.7 then install lic from 5.1.x base.  This worked really well
for us, your other procedures are good as well. (Backup db etc)

-----Original Message-----
From: Helen Tam [mailto:hht1 AT NYU DOT EDU]
Sent: Thursday, December 18, 2003 1:15 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: TSM Upgrade to 5.2 from TSM 4.2 on an AIX 5.1 Server


Hello,
    I try to get these info from IBM but they say they could not help me
unless I run into problems while doing it.  Could you help?

Are they any documents in how to install TSM 5.1.7.3? We have window
clients. Do I install TSM 5.1 base and then apply maintenances?
     environment:
     AIX 5.1 TSM 4.2.1.9 server
     IBM H50
     359x Library & 4 3590 tape drives

Also in my case with a cloned rootvg, could I do the db backup as follows:
      backup db type=full devclass=3590
      backup devconfig filename=devconfig.date
      backup volhistory filename=volhistory.date

Where do I get the backup tape volser, from the activity log?
How do I eject this backup tape from the library? We have 349x library and
drives.

And if I need to back out from the migration, could I just do a restore of
this backup tape by
issuing:
     dsmserv restore db volumes=volser(from the backup) devclass=3590
commit=yes

I need to write up a plan for our migration. Please advise.
                                                        Thanks,
                                                             Helen Tam