Verify the nametype of the node's filespaces in the TSM server. Maybe the
client expects the filespaces to be unicode but the server's node
definition does not allow automatic filespace rename. Output of `q no
c010191b f=d` and `q fi c010191b f=d` might help.
Zlatko Krastev
IT Consultant
Sascha Braeuning <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
28.11.2003 15:13
Please respond to "ADSM: Dist Stor Manager"
To: [EMAIL PROTECTED]
cc:
Subject: ANR9999D TSM Server 4.2.2.2 and Client 5.1.5.15
Hello TSMers,
I've got a problem with an updated client. We updated the Windows NT
client
from version 3.1 to version 5.1.5.15. Our TSM server is running under Z/OS
and TSM Version 4.2.2.2. I tested backup and restore behavior and
everything looks fine. The services started without a problem and the
client got his backuptime from the server (we use prompted mode).
Now I am getting this terrible error message on the TSM server:
28.11.2003 13:46:00 ANR9999D SMEXEC(1627): ThreadId<139004> Session
78272
with
client C010191B (WinNT) rejected - server does not
support the UNICODE mode that the client was
requesting.
When I check the clienterrorlogs, there seems to be everything alright. No
errors! Can anybody help?
Mit freundlichen Gr��en
Sascha Br�uning
DB/DC C/S-Systeme/�berwachungsverfahren FE/KA
Sparkassen Informatik GmbH & Co.KG
Wilhelm-Pfitzer-Stra�e 1
70736 Fellbach
Telefon: 0711/5722-2144
Telefax: 0711/5722-2147
Notes: Sascha Br�uning/6322/FE/SI/[EMAIL PROTECTED]
E-Mail: [EMAIL PROTECTED]
