One of my clients had this problem a while back.  Here's a couple of the
responses I got from this list.  Unfortunately, the workstation that was
having the problem, was replaced before anything was fully determined and
fixed.  Hope this helps some.


Hi Betsy,

I also don't know much about UNICODE but you might set
the useunicodefilenames option to yes in the client options file.
(used to provide support for MAC-files on NT)

Regards
     Mecki




Hi Betsy!
99% chance that the computer name of this client is changed.
The ADSM client tries to connect to the ADSM server using a new client name
(since the nodename is the computername if not specified otherwise in the
dsm.opt) while the server contacts the client using the old client name.
I have seen this here too. The solution is to rename the ADSM client at the
server side. Don't forget to rename de filespaces too since the computer
name is part of the UNC name.
Kindest regards,
Eric van Loon





ADSM-L AT VM.MARIST DOT EDU on 07/12/99 06:48:49 AM
Please respond to ADSM-L AT VM.MARIST DOT EDU @ INTERNET
To: ADSM-L AT VM.MARIST DOT EDU @ INTERNET
cc:
Subject: Unicode mode ?

Hi,

Has anyone seen this message or has an idea what it means?
Client version: WinNT 4.0 SP3 ADSM V3.1.0.6
Server version: OS/390 2.7 ADSM V3.1.2.20

Message: 07/12/1999 12:45:56  ANR9999D SMEXEC(1171): Session 10118 with
client
                      MAINABSATOWERS (WinNT) rejected - server does not
support
                      the UNICODE mode that the client was requesting.

This client has been working fine without changes to software levels.

Thanks
Christo Heuer