The information is muddled, in that you're saying that you're running a mixed 
cluster with both Linux and Netware, with both clients (at different levels) 
performing backups of the same data, ostensibly with the same node name.  I 
would not expect good results from that.

One query you should do on the TSM server is "Query FIlespace TEST 
Format=Detailed" to survey the filespace characteristics, seeing if there is 
some mixture of Unicode (as in UTF-8) and non-Unicode - and particularly if any 
filespaces are both, where TSM will default to trying to use the non-Unicode 
instance.

What you're doing is on the fringes of product utilization.  You may have to 
contact TSM Support to get further.  Check your dsmerror.log for further 
indications of underlying problems, as well as the TSM server Activity Log for 
problem indications at session initiation attempts.  A client trace (see TSM 
Problem Determination Guide) would reveal more.

     Richard Sims

On Jun 30, 2010, at 9:50 AM, Günther Schwarz wrote:

> Richard Sims wrote:
>> Your session hasn't gotten far enough for the problem to be file
>> issues regarding locale settings. Your problem description doesn't say
>> exactly what you've been doing, but the sense I get is that you've been
>> using the same nodename for two different clients, at two different
>> levels, which is a very bad idea, leading to numerous problems. Don't do
>> that.
> 
> I'm sorry if I did not manage to describe the problem in sufficient detail. 
> It is about NSS cluster volumes in a high availability setup. These volumes 
> do have their their own IP, host as well as nodename and move between cluster 
> servers depending on server load and availability.
> Backup of cluster volumes is covered by Jason Baseler et al. in 'Using the 
> IBM Tivoli Storage Manager Backup-Archive Client in Cluster Environments on 
> UNIX and Linux'.
> <http://www.ibm.com/developerworks/edu/tz-dw-tz-tsmbackcluster.html>
> 
> Cluster environments are an exception to the rule that a TSM nodename should 
> correspond to a single machine. Regular backups of cluster volumes demands 
> that the nodename is used on different hosts. This works well as long as all 
> hosts run the same OS and TSM client version.
> 
> My problem is related to the migration from Netware to Linux. For some 
> limited time we will run a mixed cluster where cluster volumes are backed up 
> on Netware or Linux.
> 
> What I have been doing so far: I installed the TSM client on the Linux hosts 
> and configured them for the backup of cluster volumes as described in the 
> above document. This works fine as long as the node has not been set up to 
> NTW:UTF-8 on Netware. With a filespace NTW:UTF-8 I get the error message I 
> documented in my previous mail.
> 
> Which information might still be required?
> 
> best wishes
> 
> Günther Schwarz