ADSM-L

Re: NT dr watson errors

2000-01-05 14:18:35
Subject: Re: NT dr watson errors
From: Andy Raibeck <storman AT US.IBM DOT COM>
Date: Wed, 5 Jan 2000 11:18:35 -0800
Hi Jeannine,

This could be APAR IC24882, which can occur if a file is
truncated while being processed by ADSM/TSM. A very common
file that ADSM "stumbles" over is dsmerror.log, which can
be truncated via log pruning. Try putting an EXCLUDE
statement in the dsm.opt file, then restart the scheduler.

If that does not do the trick, then please open a problem
record with IBM support so that we can do further
diagnostics.

Best regards,

Andy

Andy Raibeck
IBM
Tivoli Storage Manager Client Development
e-mail: storman AT us.ibm DOT com
"The only dumb question is the one that goes unasked."

Hello all,
I am currently running ADSM Server v3.1.2.40 on AIX.  My NT
clients are at 3.1.0.7.  They are NT servers at NT 4 SP 5.
Since I upgraded the NT servers to 3.1.0.7 I have experienced
lots of Dr. Watson errors on the NT boxes. The event log does
not report a problem.  Dsmsched.log shows the back up
beginning and waiting for a tape mount and that's it.
Dsmerror.log shows nothing.  The connection is severed, the
client gets a Dr. Watson and the service shuts down.  It must
be manually restarted.  It will then run fine for a few days
and then same thing.  It happens on all of out NT boxes both
Compaq and Dell. Anyone else seen this?  How can I fix it?
Thanks for any/all info.

Regards,
Jeannine Walter

Purina Mills, Inc.
St. Louis, MO
314-768-4181
Jeannine_Walter AT Purina-Mills DOT com
<mailto:Jeannine_Walter@Purina-> Mills.com>
<Prev in Thread] Current Thread [Next in Thread>