Called Tivoli and found out that there is a little known and experienced
"feature" where the client scheduler component on the TSM server just stops.
They say it is very rare and they haven't been able to re-create the issue
or figure out why it goes brain-dead. A reboot of the TSM server machine got
them back up and running. Tivoli asked for some query output to see if it
would help them in determining the sequence of events that lead to the
brain-dead state. He said it's been reported on different OS's and different
TSM server levels.

I've been doing TSM for 5-years and have never seen this condition. Level2
support said I would probably never see it again. That's how rare it is.

Bill Boyer
DSS, Inc.

-----Original Message-----
From: Bill Boyer [mailto:bill.boyer AT verizon DOT net]
Sent: Monday, August 11, 2003 5:08 PM
To: ADSM-L
Subject: URGENT!! TSM client schedules not running


TSM Server 5.1.7.1 on AIX 5.1 64-bit. ALl was working just fine until
2-nights ago. Half of their schedules "missed" and last night almost all of
them "missed". Right now doind testing with clientaction schedules they just
sit there in a "pending" state. They will not run unless the scheduler
services is restarted on the client. Then that and only that schedule will
run. If you turn right around and issue another clientaction for the same
node that was just restarted and processed the schedule it sits "pending".

Any help?!?!?!? I'm waiting on a call back from Tivoli support on this
sev-1.

Bill Boyer
"Some days you are the bug, some days you are the windshield." - ??