Clarence Beukes wrote:
>
> Hi There............
>
> I have a customer with ADSM V3.1.2 on OS/390 2.6; a Lotus Notes Agent on NT
> 2.1.7., and I get the message:
>
> ANR9999D-
> SMEXEC(1162)...............................................................
> ....Server does not support the UNICODE mode that the client was
> requesting.
>

It's probably the following APAR:

  APAR Identifier ...... IC22325      Last Changed ........ 99/03/30
  ADSM GUI DOES NOT FUNCTIONING WHEN FIRST TIME EXECUTED
  AFTER NETWORK COMPUTER NAMECHANGED AND PASSWORDACCESS GENERATE

  ERROR DESCRIPTION:
  When passwordaccess is set to generate and
  you change mashine name, when you start GUI
  for the first time it rises Communication protocol
  error message, it not actually hang but b/a
  and some other functions is disabled, nobody
  prompts for password, At the server side we
  have in activity log:
  ANR0424W Session 101 for node BLUE.OUCS (Win95)
  refused - invalid password submitted.
  ANR0403I Session 101 ended for node BLUE.OUCS
  ANR9999D smexec.c(1041): Session 102 with client
  BLUE.OUCS (Win95) rejected - server does not
  support  the UNICODE mode that the client was
  requesting.
  If you close and restart GUI it prompts for password and problem
  never happens again unless you turn passwordaccess generate
  off and then on and change mashine name again.

  LOCAL FIX:
  Close and restart GUI and enter password. You will have no
  this problem again until toggle passwordaccess generate
  and mashine name change.
  Or do not use passwordaccess generate.

Gerhard