Re: "ANR2020E Invalid parameter - ORIGINATOR". from v3 admin cli
2015-10-04 18:03:06
Subject: |
Re: "ANR2020E Invalid parameter - ORIGINATOR". from v3 admin cli |
From: |
Lambelet,Rene,VEVEY,FC-SIL/INF. |
To: |
ADSM-L AT VM.MARIST DOT EDU |
Hello,
we installed the server MVS 3.1 yesterday. Since then, this problem
disappeared, it is now ok.
I guess the originator is only recognised by the 3.1 server.
Regards
Rene Lambelet, Nestle, VEVEY
>-----Original Message-----
>From: Virginia Hysock [SMTP:Virginia_L_Hysock AT CSC DOT COM]
>Sent: Monday, December 08, 1997 4:21 PM
>To: ADSM-L AT VM.MARIST DOT EDU
>Subject: Re: "ANR2020E Invalid parameter - ORIGINATOR". from v3 admin cli
>
>Yes. I have been unable to use the Activity Log as well. I am running the
>NT 3.1 client on a
>NT 4.0 machine. I get the same error message.
>
> Also - when filtering the scheduled events log, requesting just
>administrative scheduled events or
>backup/archive scheduled events does not work; I still get everything.
|
<Prev in Thread] |
Current Thread |
[Next in Thread> |
- "ANR2020E Invalid parameter - ORIGINATOR". from v3 admin cli, Alex Mounayar
- Re: "ANR2020E Invalid parameter - ORIGINATOR". from v3 admin cli, Virginia Hysock
- Re: "ANR2020E Invalid parameter - ORIGINATOR". from v3 admin cli, Lambelet,Rene,VEVEY,FC-SIL/INF.
- Re: "ANR2020E Invalid parameter - ORIGINATOR". from v3 admin cli, Eric van Loon
- Re: "ANR2020E Invalid parameter - ORIGINATOR". from v3 admin cli,
Lambelet , Rene , VEVEY , FC-SIL/INF . <=
|
|
|