Trevor, Pascal,
thanks for your replies.
Seems there is another good reason for IBM to bring out a V3 for VM :-)

I have heard the V3 server has been completely rewritten (?) 
But as all platforms share the same codebase (I asume) - how big
could the effort be to create a V3 for VM (and all the other platforms
still on V2)?

As I start to install ADSM now, a lot of questions will follow.
Thanks for your support.

Kind regards
Thomas Rupp  

> -----Ursprüngliche Nachricht-----
> Von:  Pascal DESTOUCHES [SMTP:pascal.destouches AT CEGEDIM DOT FR]
> Gesendet am:  Montag, 6. Juli 1998 08:35
> An:   ADSM-L AT VM.MARIST DOT EDU
> Betreff:      Re: ANR2020E Invalid parameter - ORIGINATOR.
> 
> Hi Thomas,
> 
> We also had this problem : we have ADSM server V2 onto VM, and we
> tried to install a Win95 client V3. At that time, we can't do any
> admin commands thru the GUI (we got the same error ORIGINATOR
> problem).
> 
> Since V3 server is not yet announced on VM, you have to leave V2
> client on platforms you wish to do admin stuff.
> 
> Have a nice day,
> 
> Pascal;
> 
> -----Message d'origine-----
> De:     ADSM: Dist Stor Manager [SMTP:ADSM-L AT VM.MARIST DOT EDU] À la place
> de Rupp Thomas (Illwerke)
> Date:   samedi 4 juillet 1998 15:13
> À:    ADSM-L AT VM.MARIST DOT EDU
> Objet:  ANR2020E Invalid parameter - ORIGINATOR.
> 
> Hi ADSM gurus!
> I've a small problem with the ADSM Administrative Client
> (3.1.01) on Windows NT 4.0 (SP 3). Server is ADSM for VM
> 2.1.0 without PTF's.
> 
> I've changed the Activity Log include message times to narrow
> the amount of messages. But now I always get the message
> 
> ANR2020E Invalid parameter - ORIGINATOR.
> 
> even if I reset the values.
> Has anybody seen this problem before?
> 
> Kind regards
> Thomas Rupp
> Vorarlberger Illwerke AG
> thomas.rupp AT illwerke.co DOT at