Recently, for migration/testing purposes, I did a full conversion of a 5.5 server to 6.2 on my test TSM server.
I would like to continue using this server to test additional upgrades without having to wipe and rebuild. Unfortunately, since it is a copy of a real server, whenever I fire it up, it keeps trying to "reach out and touch" other TSM servers that it has definitions to (library manager, etc), thus producing constant error messages due to invalid passwords, etc. I am concerned if I play with it to do like things mass-deletes, etc, it will try to do things like purge/release tapes, etc. Besides adding to DSMSERV.OPT: DISABLESCHEDS YES NOMIGRRECL What else can I do to neuter it to avoid possible problems? In this same vein, is there a simple way to remove the current instance and install/configure another one? Zoltan Forray TSM Software & Hardware Administrator Virginia Commonwealth University UCC/Office of Technology Services zfor...@vcu.edu - 804-828-4807 Don't be a phishing victim - VCU and other reputable organizations will never use email to request that you reply with your password, social security number or confidential personal information. For more details visit http://infosecurity.vcu.edu/phishing.html
