Re: "ANR2020E Invalid parameter - ORIGINATOR". ressource consump.

Hello,

it seems that ADSM is still very "gourmand" in CPU, eating a lot of a
112 mips bi-pro.
About the storage used, we have now about 140 MB in extended storage
instead of 128 MB with version 2.1.

N.B. no special tuning has been done.

Our server options:

Server Option           Option Setting          Server Option           Option
Setting
-----------------               --------------------            
-----------------
                --------------------
                --------------------
CommTimeOut             2,000                   IdleTimeOut             15
BufPoolSize             90000                   LogPoolSize             4096
DateFormat              1 (mm/dd/yyyy)          TimeFormat              1 
(hh:mm:ss)
NumberFormat            1 (1,000.00)            MessageFormat           1
Language                AMENG                   MaxSessions             50
ExpInterval                     0                               ExpQuiet        
                No
MirrorRead DB           Normal                  MirrorRead LOG          Normal
MirrorWrite DB          Sequential              MirrorWrite LOG         Parallel
VolumeHistory           'ADSM.VOLSTOR'  VolumeHistory            'ADSM.VOLSTOR2'
Devconfig                       'ADSM.DEV.DATA'         Devconfig               
        'ADSM.DEV2.DATA'
TxnGroupMax             256                             MoveBatchSize           
256
MoveSizeThresh          500                             StatusMsgCnt            
10
RestoreInterval         1,440                   UseLargeBuffers         Yes
CommOpenTimeOut         20                              TcpPort                 
        nnnnn
TcpName                 TCPIP                   IcsPort                         
nnnn
IcsSname                *NONE*                  UserExit
FileExit                                                HttpIcsPort             
        nnnn
HttpTcpPort             nnnn                            DeletionExit            
        ARCTVEXT
MsgSuppress             *NONE*                  LuName                  *NONE*
Iucv                            *NONE*                  RouteCode               
11
MsgHilight                      *NONE*                  MPThreading             
No
TCPBufsize              32,768                  HPDTenable              Yes
HPDTstorage             ECSA                    HPDTbuffer#             6
HPDTexpand#             2                               TECHost
TECPort                         0


Regards, Rene Lambelet

>-----Original Message-----
>From:  Eric van Loon [SMTP:evanloon AT KLM DOT NL]
>Sent:  Tuesday, December 09, 1997 8:54 AM
>To:    ADSM-L AT VM.MARIST DOT EDU
>Subject:       Re: "ANR2020E Invalid parameter - ORIGINATOR". from v3 admin cli
>
>Hi Rene (or anybody running the MVS 3.1 server),
>Have you seen any difference in CPU utilisation with V3.1?
>Kindest regards,
>Eric van Loon
>
>----------
>From:  Lambelet,Rene,VEVEY,FC-SIL/INF.
>Sent:  Tuesday, December 09, 1997 07:50
>To:    ADSM-L AT VM.MARIST DOT EDU
>Subject:       Re: "ANR2020E Invalid parameter - ORIGINATOR". from v3 admin cli
>
>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.
>
>