Herfried,

Thanks for your response.

Looking on the server admin console indicates that the filespace is not
unicode:
Is Filespace Unicode? NO

Do you know of anything else that could cause this problem?

Chris

> -----Original Message-----
> From: Herfried Abel [mailto:ha7 AT DAIMLERCHRYSLER DOT COM]
> Sent: 07 March 2002 10:04
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: Linux and Windows clients
> 
> 
> chris,
> I think using the win client sets the nodes filespaces to 
> unicode enabled
> within the tsm internal database. This causes your error. you 
> can reset the
> client only
> using the "non documented" SET RECORD method. ( This manipulates the
> internal db and should only be used on IBM/Tivoli advice.)
> 
> Maybe you could fake the client-api so that the win client shows up as
> Linux ?
> 
> herfried
> 
> 
> 
> 
> Chris West <Chrisw AT CRISTIE DOT COM>@VM.MARIST.EDU> on 07.03.2002 10:34:32
> 
> Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
> 
> Sent by:  "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
> 
> 
> To:   ADSM-L AT VM.MARIST DOT EDU
> cc:
> 
> Subject:  Linux and Windows clients
> 
> 
> Hello,
> 
> I'm quite new to ADSM so please forgive me if I'm asking something
> stupid.
> 
> I am trying to connect to a TSM server (4.2.1) using both Linux and
> Windows clients (home made clients built using the API).
> Both clients need to connect to the same client node and the same
> filespace.
> The Windows client will be used for backing up and and the 
> Linux one for
> restoring.
> 
> The Windows client can backup OK but the Linux client is unable to
> connect.
> 
> dsmInit returns:
> ANS1357S (RC57)   Session rejected: Downlevel client code version
> 
> Both clients are built using the same API version (4.2.1).
> 
> Is there a way I can access the same filespace from these 2 clients?