Hi Ginny, I have a similar set up, except my database is half that size.
I'm using 144MB region size, and yes, that's alot.
However, when we first converted to 3.1.1.3, we used 128M and it was fine.
My bufpoolsize is only 8192 though!!
Julie




Virginia Hysock <Virginia_L_Hysock AT CSC DOT COM> on 08/04/98 07:34:32 AM

Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>

To:   ADSM-L AT VM.MARIST DOT EDU
cc:    (bcc: Julie Phinney/Green Bay/Humana)
Subject:  Server Abending





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 set
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