We have been experiencing the buf006 errors for the last week.  After increasing
the bufpool parameter numerous times, the server was still crashing.

We just changed to the maxperm -P variable in /usr/samples/kernel/vmtune.  The
setting
has been modified in the /etc/noOptionsForADSM.stsm script used during startup.
The -P setting will now be 50 versus the default setting.  When viewing the new
value you'll see a value of 65531.  The original value was 104031.





From: O1=INET00/C=US/A=IBMX400/P=STATEFARM/DD.RFC-822=ADSM-L\@VM.MARIST.EDU on
08/31/99 09:23:36 PM
To:   ADSM-L
cc:
Subject:  Re: Server crashed - BUF043.

I'd say it's running out of memory..;-)

IT would appear you have more than enough system
resources to house a large ADSM server.

You might try messing with the bufpool
sizes if Dave's statement is indeed accurate.

Dave's comments, under assumption here, are based on past
experiences through PMR/APAR databases which house all old
instances of ADSM issues.  Some may be first-hand knowledge,
but the average issue does not get to a developer.

To say ADSM is the only app running tends to be misleading.
You could very well have SP and HA related daemons running
in the background in addition to the typical AIX daemon
outline.

I sure someone out there can tell you what fileset contains
the vmtune executable.  Anyone?

ADSML

>David, how did you determine that 50 was the optimum number?
>
>Our server has 256MB RAM. Page space is 512MB.  The ADSM
>server is the only application that is running in our SP wide node.
>
>Is 50 the optimum for our configuration?
>
>Also I've just found out that our system does not have the vmtune
>command.  Do we need a PTF?
>Your suggestion is appreciated.
>Angel

> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On
> Behalf Of ANGEL BUGARIN
> Sent: Tuesday, August 31, 1999 9:01 PM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      Re: Server crashed - BUF043.
>
>  << File: BDY.RTF >>