We have done the same thing as well.
If you want more detail on the plan, I would do the following:

.1      Only needs to be done once, but load the upgrade utilities on the 
server to be upgraded

.2      Backup 5.5.4 Database

4       extract the database .....(when I extract the db I always put the 
manifest file on the /upgrade filesystem)
4.1     Copy devconfig & volhist to /upgrade  (grabs the devclass for the 
extracted file)

5.1     copy devconfig & volhist from /upgrade to /home/<tsminst1>     (usr 
name of new 6.2.4 instance owner)
        Check permissions on files

5.2     dsmserv removedb TSMDB1   
5.3     cleanup directories that hold the db2 db, db2 log, db2 logm, db2 
archlog, db2 arch failover by removing files
5.3     format database to meet sizing requirments      
6.1     set dbrecovery
6.2     backup new 6.2.5 TSM db

No ideas on what the prepared db does.

~james
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Lee, Gary
Sent: Wednesday, February 27, 2013 10:03 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] upgrae from 5.5.4 to 6.2.4

So far, sounds good.
This is my plan.

1. run prepared on 5.5.4 server.

Two create a file devclass on 5.5.4 server pointing to /upgrade.

3. mount a file system from the new tsm server onto /upgrade.

4. extract the db to /upgrade.

5. restart the 5.5.4 server for production work.

6. do the insert on the 6.2.4 server.

Does this look reasonable?

I have so far not found an explanation of what the dsmupgrd prepared does.

Any ideas?

Gary Lee
Senior System Programmer
Ball State University
phone: 765-285-1310

 

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Huebner, Andy
Sent: Wednesday, February 27, 2013 9:41 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] upgrae from 5.5.4 to 6.2.4

We did an upgrade from 5.4 to 6.2.
I used a copy (SAN trick) for the source of the upgrade.  I do not think the 
5.5 to 6.2 upgrade changed the copy, I did not check, but I did not see any 
writes to the disks.  The extract was written to a new disk.  We created a new 
devclass (file) to write the data to.
Our about 200GB DB took about 3 hours to extract, the insert to 6.2 took 
10+hours.  This was done on a P6.
We did 3 practice upgrades for each server.  Only 1 upgrade test failed because 
we did not get a clean copy.

You might consider 6.2.5 as your target.

Good Luck.

Andy Huebner


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Lee, Gary
Sent: Wednesday, February 27, 2013 8:20 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] upgrae from 5.5.4 to 6.2.4

I want to do a couple of practice upgrades of our tsm server v5.5.4 to a 
different box running v6.2.4.

Reading the upgrade guide, I have to do the 

Dsmupgr prepared

Then a 

Dsmupgrd extractdb

I have not yet determined whether these will render the 5.5.4 server unusable?

Has anyone out there done this and if so, what should I expect?

Gary Lee
Senior System Programmer
Ball State University
phone: 765-285-1310