Well let's not limit it to after a V3 upgrade!

     Our two MVS ADSM environments would suck up more CPU (memory, cycles,
     you name it) than any other started task (even all our CICS regions
     combined!

     Due to the lack of flow of funny money they cut back our cycles to the
     point we've purchased two new S-70 to move the mvs adsm work load over
     to.

     Which is a big NOTE! your system programmers / system tuners can make
     or break adsm under MVS so watch'em ;-)

     Now I never got our buffpool or logpool that big and we never ran with
     more than 150 concurrent sessions for what thats worth...

     Anyway, good luck and if you have any questions on ADSM under AIX just
     give me a yell... ;-)

     later,
            DWight


______________________________ Reply Separator _________________________________
Subject: Server Abending
Author:  Virginia.L.Hysock (Virginia_L_Hysock AT csc DOT com) at unix,mime
Date:    8/4/98 7:34 AM


OS/390 2.4 MVS Server, just converted to 3.1.1.3, with a mirrored 18 GB database
AIX, HPUX, Windows, NT, Netware clients (300+)

Hi all,

     I finally upgraded my ADSM server over the past weekend from 2.1.13 to
3.1.1.3.  Everything was looking great until my first set of scheduled backups
kicked in Monday night.  My server abended several times with various messages,
including ANR0529W Insufficient Memory on the server.  I have my buffpoolsize se
t
to 24576, my logpoolsize set to 8192 and maxsessions set to 325.  The messages
manual recommends decreasing all of these settings and/or increasing the memory
allotted to the server.  My MVS tech says that 128M (which is recommended in the
Quick Start Guide) is a lot already.

     Anyone else ever experience a similar problem after upgrading?  I am hoping
to resolve this before too many days go by, in case I am forced to back out the
new level.  TIA,

                              Ginny