On Wed, 13 Aug 2003 13:56:21 -0400
"Adams, Matt (US - Hermitage)" <maadams AT DELOITTE DOT COM> wrote:

> I would doubt that you will never see it again.
>
> We're on TSM server version 5.1.6.2 and have seen it one more than one
> occasion in the past 6 months.
>
> Regards,
>
> Matt
>

What is surprising is that apperently quite some people on this list have
this problem on a regular basis, but apperently, nobody bothers to open a
PMR on this with tivoli support... We al have support on our servers, right?
So why not use it to help tivoli solve the problems we see?


> -----Original Message-----
> From: Bill Boyer [mailto:bill.boyer AT verizon DOT net]
> Sent: Wednesday, August 13, 2003 12:45 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Resolved: URGENT!! TSM client schedules not running
>
>
> 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." - ??
> This message (including any attachments) contains confidential information
> intended for a specific individual and purpose, and is protected by law.
> If you are not the intended recipient, you should delete this message.
> Any disclosure, copying, or distribution of this message, or the taking of
> any action based on it, is strictly prohibited.


--
Met vriendelijke groeten,

Remco Post

SARA - Reken- en Netwerkdiensten                      http://www.sara.nl
High Performance Computing  Tel. +31 20 592 8008    Fax. +31 20 668 3167

"I really didn't foresee the Internet. But then, neither did the computer
industry. Not that that tells us very much of course - the computer industry
didn't even foresee that the century was going to end." -- Douglas Adams