After reinstalling the OS and ITSM binaries you will need two registry
keys:
HKLM\Software\IBM\ADSM\CurrentVersion\Server\Server1
HKLM\System\CurrentControlSet\Services\TSM Server1

Probably the easiest way would be:
- rename ..\server1 directory
- create instance using same directory without overwriting DB, Log &
stgpool files
- stop the blank instance and delete so created directory
- rename back old ..\server1
(have in mind I did not tested it this way)

Zlatko Krastev
IT Consultant






Ken Sedlacek <Ken_Sedlacek AT KYRUS DOT COM>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
06.10.2003 20:57
Please respond to "ADSM: Dist Stor Manager"


        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        For a W2K TSM 5.1.6.3 server program reload: Why won't 
TSM server restart
as before?


Enviro:

W2K TSM 5.1.6.3 server.

Original W2K TSM 5.1.6.3 program on "C" drive.

Running for months with no-problems!

DB, recovery logs, and ..\server1 files on "D" drive.

The W2K OS on "C" drive needed to be reloaded to fix corrupted OS files.

The "D" drive was never touched and remained as it was before the "C"
drive OS reload.


Question:
What is the proper way to reload the TSM server program files and use the
existing DB, recovery log, and ...\server1 files to continue using TSM the
way it was before the W2K OS reload?

I do have a current DB tape & ...server1\*.* files I can use if need be.


Ken Sedlacek
AIX/TSM/UNIX Administrator
ksedlacek AT kyrus DOT com
Agilysys, Inc. (formerly Kyrus Corp.)

IBM eServer Certified Specialist: pSeries AIX v5 Support
IBM Certified Specialist: RS/6000 SP & PSSP 3
Tivoli Certified Consultant - Tivoli Storage Manager v4.1