I'm surprised you can run with a region that small, we are running
     version 2.1, ptf 13 in a 300m region.  We had several problems with
     0c4 abends and IBM recommended increasing our region size and since we
     did that we haven't had any abends.
     james.sporer AT doit.wisc DOT edu



______________________________ Reply Separator _________________________________
Subject: Server Abending
Author:  "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>  at IPNET
Date:    8/4/98 8: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
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