Hi Stephanie,

You can not do anything about it (Apart from increasing the Idletimeout
parameter),
I believe IBM should do something about the code so it tells the ADSM server
that the client is in fact still busy doing processing although the session
state is IdleW. We have two servers where this behaviour has been an issue.
We
increased the idletimeout to 60 and the server completes. Have a look at
your
directory structure on the client machine - you will find this server has in
excess
of 100000 files in a certain directory - while ADSM is still busy getting
the list
of files on the client machine it is in Idlew status untill the list is
complete.

The only problem is that by increasing the Idletimeout parameter it is
applicable
to all sessions on the server - so if you have plenty of server finishing of
at
more or less the same time you'll have many sessions sitting there waiting
for
the timeout parameter of 1 hour - If you are limited on the ADSM server in
terms
of sessions that you can run concurrent then this becomes an issue.

Regards
Christo Heuer
ABSA Bank
Johannesburg
South Africa

> Hi,
>
> On  NT servers (ADSM 3.1.0.6), I have a backup scheduled every night.
> The DOMAIN option is set to ALL LOCAL.
>
> Every night, on 3 of these servers, we have the same problem :
> The backup of the C: partition is made with no problem, and then when
backing up
> the D: partition, the backup hangs, during one hour (the TIMEOUT on the
server
> (MVS 3.1.2.20) is set to 60). And then the session is terminated by the
server.
>
> Does any body already have this problem?
> What is wrong with our NT servers?
>
> Thanks for your help