Rajesh,

I had problems with Unix clients.As per the logs it would show that
dsmsched.log shows only part of the job run and stopped.

Check ur memeory size being utilized if there is memory leak this would
occur.On Unix we have tools that help to work around this issue.

I think u need to update NT as well as TSM patches.

These got eliminated on Unix machines after I updated to latest level of
Patches.
You may also see that so other application may be gobbleing memory leaving
no room for TSM Client.

Balanand Pinni

-----Original Message-----
From: Rajesh Oak [mailto:rajeshoak AT lycos DOT com]
Sent: Friday, March 07, 2003 1:06 PM
To: ADSM-L AT VM.MARIST DOT EDU
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