>You know, there seems to be a similar issue with filespace naming with the new Netware cluster aware client. >We're awaiting a server upgrade to pursue it further. Seems as it the 'getservername' API call is at the heart of this.
Yes, it seems TSM is not savey of any cluster soloutions except Microsoft's. If they (TSM) would only introduce a new option in the .opt file so one could override the servername if for some reason or another one should wish to do so. It would probably solve the naming problem in most cluster sitiations. Regards Peter
