You should contact IBM support if you are having this kind of problem. I
am not aware of any problems that could cause what you are seeing. If you
haven't already done so, take a look at the Application and System Event
logs to see if anything abnormal was logged. You also might check the
dsmerror.log file, the dsmwebcl.log file (if using the CAD to manage the
scheduler), and the server activity log from the time the client backup
began through the time it terminated, to see if anythere there might shed
some light on the problem.

4.2.1.30 is the latest patch level. Normally we don't steer customers to
patches from the web site because the patches should only be applied (in
theory) at the direction of IBM service or development to resolve specific
problems. However, due to substantial problems at the 4.2.1.0 level, we do
not recommend that users install that level; so when we issued 4.2.1.20,
we did more extensive testing of that client code than is usual for a
patch. That is why the web site points to it.

Regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: storman AT us.ibm DOT com

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.




Keith Kwiatek <kkwiatek AT NIST DOT GOV>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
04/10/2002 08:15
Please respond to "ADSM: Dist Stor Manager"


        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        TSM 4.2.1.30 scheduler dies intermittently....



Hello,

I have  900 tsm total TSM clients. Everything has been running fine, but I
have 20 new clients that have installed TSM 4.2.1.30 on their win2000
machines. The tsm scheduler starts fine, and at the correct time begins a
backup. But sometimes the scheduler just dies. Doesn't leave errors
messages. I look at the end of the dsmsched.log and I can see that it was
in
the process of backing up (files are being "sent'), but then it just ends.
The last entry is just a file being sent to the server, and then nothing.
The scheduler is stopped in "services".

The machine is not being powered down. There is no power managment. These
are experienced users.

One curious thing is that Tivoli now has 4.2.1.20 as the latest win2000
client -whereas I had downloaded tsm 4.2.1.30 not too long ago (??) Why
are
they going backwards?

Any and all help is appreciated!!

Keith