Hi Gordon!
The way to prevent the installation from doing a upgradedb is to hide the
database during installation. You can easily do this by renaming the
dsmserv.dsk file before upgrading.
Kindest regards,
Eric van Loon
KLM Royal Dutch Airlines


-----Original Message-----
From: Gordon Woodward [mailto:[EMAIL PROTECTED]
Sent: Friday, August 06, 2004 06:10
To: [EMAIL PROTECTED]
Subject: TSM 5.2 Upgrade and Maintenance releases


I want to upgrade our TSM servers next week to v5.2.3 from 4.2.4.1. I was
going to install TSM server 5.2 first and then the 5.2.3 maintenance release
over the top. What file is it that needs to be moved/renamed to stop the
database being upgraded after v5.2 is installed so I can do a manual upgrade
later? I only want to do one upgrade but can't find any information on the
IBM support website.

Thanks,

Gordon Woodward



--

This e-mail may contain confidential and/or privileged information. If you
are not the intended recipient (or have received this e-mail in error)
please notify the sender immediately and destroy this e-mail. Any
unauthorized copying, disclosure or distribution of the material in this
e-mail is strictly forbidden.


**********************************************************************
For information, services and offers, please visit our web site: http://www.klm.com. 
This e-mail and any attachment may contain confidential and privileged material 
intended for the addressee only. If you are not the addressee, you are notified that 
no part of the e-mail or any attachment may be disclosed, copied or distributed, and 
that any other action related to this e-mail or attachment is strictly prohibited, and 
may be unlawful. If you have received this e-mail by error, please notify the sender 
immediately by return e-mail, and delete this message. Koninklijke Luchtvaart 
Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for 
the incorrect or incomplete transmission of this e-mail or any attachments, nor 
responsible for any delay in receipt.
**********************************************************************

Reply via email to