We've been chasing the same problem for months. IBM gave us 3 options, the
easiest one to change was the options file which is what we did and
haven't seen the problem return in either 2.1.5 or with ptf6. You might
want to try adding:

SCHEDMODE PROMPTED

to your options file. That option seems to use enough less memory on the
client that it doesn't hang.

You might want to check the error logs on the client also to see if they
show any problems. One of the people that reported a problem was on a
shared terminal and SOMEONE was issuing a CNTL-C but no actually blowing
the scheduler icon away so it HUNG and made it look like the scheduler was
up when it had been closed. .

Julie Phinney wrote:

> I'm not too familiar with Win 95. One of our Win 95 users was notified
> that his ADSM wasn't backing up, and he noticed that the scheduler
> seemed to be suspended.  The last thing he'd done to it was ALT-TAB to
> it (from Rumba)  then ALT-TAB back to Rumba.  I booted up a Win 95 and
> tried this myself, and sure enough, the clock in the scheduler stops
> counting down when you ALT-TAB to it.  Does ALT-TAB act to suspend the
> ADSM scheduler?
> Thanks for any help..
> Julie Phinney
> JPHINNEY AT HUMANA DOT COM



Julie Phinney wrote:

> I'm not too familiar with Win 95. One of our Win 95 users was notified
> that his ADSM wasn't backing up, and he noticed that the scheduler
> seemed to be suspended.  The last thing he'd done to it was ALT-TAB to
> it (from Rumba)  then ALT-TAB back to Rumba.  I booted up a Win 95 and
> tried this myself, and sure enough, the clock in the scheduler stops
> counting down when you ALT-TAB to it.  Does ALT-TAB act to suspend the
> ADSM scheduler?
> Thanks for any help..
> Julie Phinney
> JPHINNEY AT HUMANA DOT COM



--
    Bill Ball
    Bill Ball
   Email: WBALL AT KENT DOT EDU

     ()_()   ()*()
      (_)     (_)

Have a Disney day.