Some old versions of the client had memory leaks but were fixed long time
ago. If you are using such an old version (many people still do not
describe their environment asking questions) the problem can show up.
There is generic solution to this - use Client Acceptor Daemon (dsmcad).
It would start and stop the TSM scheduler for each event. As result memory
leak will last only during the session and will do no harm. As side effect
any change to dsm.opt will not require restart of the scheduler (dsmcad
will take care of this).

Zlatko Krastev
IT Consultant






Rajesh Oak <rajeshoak AT LYCOS DOT COM>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
07.03.2003 21:05
Please respond to rajeshoak


        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        Scheduler stopping with error "Program Memory Exhausted"


I have a number of Win2K clients where I have seen the TSM Scheduler
stopping with error "Program Memory Exhausted". This happens after the
Windows Server has been backing up for a couple of weeks without any
issues. And suddenly it misses a schedule because of this error.
Does anyone know about a fix?
Some of the Windows NT 4.0 clients also give the same errors but is more
prevalent in Win2K servers.
Any help is appreciated.


_____________________________________________________________
Get 25MB, POP3, Spam Filtering with LYCOS MAIL PLUS for $19.95/year.
http://login.mail.lycos.com/brandPage.shtml?pageId=plus&ref=lmtplus