Joe,
I don't recall what platform you are running your ADSM server on.  In AIX
I believe the dsmserv processes all share a chunk of memory with each other,
so it may not be as much aggregate memory as you think it is.  Perhaps IBM
can shed some further light on this.

ADSM has a certain minimal number of threads (dsmserv processes).  Beyond
the minimum, it requires extra threads for each session.  One way to limit
the number of dsmserv processes would be to limit the number of concurrent
backup sessions that can run at a time (in dsmserv.opt).  There is also a
SET MAXSCHEDSESSIONS to control the maximum number of scheduled sessions.
..Paul
--
On Fri, 22 Nov 1996 17:09:48 -0500 Joe Morris said:
On Fri, 22 Nov 1996 17:09:48 -0500 Joe Morris said:
>I noticed today that when the server starts, it launches aboout 3 dozen
>"dsmserv quiet" processes each wanting 3.4Mb of memory.  This host only
>has 64MB at the moment.  I realize that this is not ideal and we are still
>testing all services and evaluating what kind of hardware we will need on
>a permanent basis when we go live with this system.
>
>In the mean time, how do I keep dsmserv from launching so many copies of
>itself?  Is there a command line option?
>
>_______________________________________________________________
>Joe Morris  -  morris AT unc DOT edu  -  http://sunsite.unc.edu/morris
>Academic Technology and Networks (formerly OIT), Development
>University of North Carolina at Chapel Hill