Please clarify:

"Everyone on AIX Server PTF level 2.1.5.12 to apply this fix"


or,

do you want MVS calls ?

Mike

 Matt Anglin writes:
 > Classification:
 > Prologue: From the desk of  Matt Anglin, ADSM Development
 > Epilogue:
 >
 > First, the bad news: IC16493 was opened against the incorrect server level.  
 > It
 > has been closed, and APAR IX65944 has been opened for this problem.
 >
 > Now the good news: The fix for IX65944 has been placed on 
 > index.storsys.ibm.com
 > in adsm/temp as IX65944.tar.Z.
 > This contains a small readme and a replacement dsmserv executable.  Make sure
 > you download it in binary and uncompress it before you untar it.
 >
 > I encourage everyone running PTF 12 to install this fix, since the problem 
 > may
 > show itself in a variety of fashions (most of which related to insufficient
 > memory).
 >
 > Matt Anglin
 > ADSM Development
 >
 >
 >
 >
 >         owner-adsm-l @ VM.MARIST.EDU
 >         02-11-97 08:39 AM
 > Please respond to ADSM-L AT VM.MARIST DOT EDU@internet
 >
 >
 > To: ADSM-L @ VM.MARIST.EDU@internet
 > cc:
 > Subject: Re: Problems with ADSM Server PTF 12
 >
 > Trevor,
 >
 > Thanks a lot for posting your warning about 2.1.5.12 and the server
 > failing due to insufficient memory - it made us double check our small
 > "test" server and you are perfectly correct, with more than very modest
 > DB bufferpool and LOG pool sizes the server fails ANR0358E. We had
 > intended to upgrade our production server tomorrow but we won't now!
 >
 > [The APAR in question is IC16493, I believe.]
 >
 > In fact, this makes 2.1.5.12 unusable for sites such as us who cannot
 > run with the DB and LOG bufferpool sizes set so low - the system
 > performance is just not acceptable. We run with a DB bufferpool of
 > 32MB and await 2.1.5.13 to have higher values which would enable us
 > to better utilise available memory on our RS6K.
 >
 > I am disappointed that this particular type of problem has arisen again
 > - there was a similar (in end result, if not ANR message) at 2.1.5.6
 > and 2.1.5.7 and 2.1.5.8, all of which were unusable here.
 >
 > It would be very helpful to know whether this fault will be fixed at
 > 2.1.5.12 or whether we have to now wait for 2.1.5.13 (or later)?
 >
 > Thanks. Regards, Sheelagh
 >
 >
 > ------------------------------------------------------------------------------
 > Sheelagh Treweek                         Email: sheelagh.treweek AT 
 > oucs.ox.ac DOT uk
 > Oxford University Computing Services     Tel:   +44 (0)1865 273205
 > 13 Banbury Road, Oxford, OX2 6NN, UK     Fax:   +44 (0)1865 273275
 > ------------------------------------------------------------------------------