Tom -
Is there anything in the works to have ADSM send out 25 simultaneous
requests and
simply collect the responses as they roll in rather than wait for each
response before sending a new one. ADSM should be able to handle this
considering the robust nature of ADSM.
Here is our sob story...
 I have 2500 clients to backup each night across the LAN and WAN at
various line speeds. The worst case scenario
is that I have to factor in 4.14 hours additional to my backup window to
compensate, not to mention retries. This seems to be ridiculous.

Thanks for the info though!
CR

________________________
Cris Robinson
Senior Technical Analyst
Desktop Services Technical Support
Liberty Mutual Insurance
603.431.8400.54837
cris.robinson AT libertymutual DOT com

> -----Original Message-----
> From: Tom Brooks [SMTP:tbrooks AT VNET.IBM DOT COM]
> Sent: Tuesday, March 10, 1998 10:50 AM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      Simultaneous client sessions parameter not working
>
>  There are some to take into consideration. The MAXSESSIONS value is
> incremented by prompted sessions, polling sessions, and admin
> sessions.
> When an attempt is made to prompt a client there is a 1 minute delay
> for
> response from that client. The next client to be prompted is not
> prompted
> until either the first client respondsor the 1 minute delay elapses.
> So if
> you have many prompted clients, be sure your schedule starttime
> duration is
> large enough to accomodate 1 minute delays. Typically the client will
> start
> as soon as prompted, so you may have prompted clients that are not
> "loaded"
> and consequently the entire delay is used waiting for a client that is
> not
> going to respond.
>  As an aside, even if you are maxed out on the MAXSESSIONS value, you
> can
> always start more administrative clients.
>
> Tom Brooks
> ADSM Development