I'm not sure what kind of elaboration you are looking for regarding my
November 18 post. What part do you need me to elaborate on?

But in answer to your question near the bottom of this post, this would be
initiated external to TSM. As to whether it is user or system-initiated, I
can not say for sure. I guess if I had to pick one, I'd say user... but
then someone could also have automated something that triggers this event.
For example, those messages could have been logged if the system was shut
down and rebooted while in the middle of a backup, or if the scheduler was
stopped, then restarted. If the backup window was still open, then the
scheduled backup would have restarted, as QUERY EVENT showed you.

As to what the *exact* cause of this is, I can't say. But there is nothing
here to suggest a problem with TSM itself. (Doesn't mean it can't be a
heretofore unknown TSM problem, but the fact that the scheduler is
restarting on its own suggests some intervention external to TSM.)

Your message implies that this has happened more than once, but you don't
say how many times. If it is happening multiple times, then you and/or the
machine's owner/administrator will need to play "detective" to get a
better understanding as to what is happening on the system. Some questions
to ask yourself: Does it happen at around the same time every night? When
did it start to happen? What changes were made to the system or network
around the time this started to occur? Is this a (usually) unattended
server, or is it a user workstation? Is there anything in the Windows
Event Log around that timeframe that might shed some light on the matter?
And so on....

Regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: [EMAIL PROTECTED]

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




"Malbrough, Demetrius" <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
11/30/2001 10:41
Please respond to "ADSM: Dist Stor Manager"


        To:     [EMAIL PROTECTED]
        cc:
        Subject:        FW: ConsoleEventHandler() Messages



Andy Raibeck, I saw your explanation on Nov. 18th, can you elaborate!

-----Original Message-----
From: Malbrough, Demetrius
Sent: Friday, November 30, 2001 11:27 AM
To: 'ADSM: Dist Stor Manager'
Subject: ConsoleEventHandler() Messages


Hi *SM'ers!

During nightly scheduled backups on one of my NT clients I am experiencing
the following messages in the dsmerror.log:

1/29/2001 22:57:15 ConsoleEventHandler(): Caught Logoff console event .
11/29/2001 22:57:15 ConsoleEventHandler(): Process Detached.
11/29/2001 22:57:26 ConsoleEventHandler(): Caught Logoff console event .
11/29/2001 22:57:26 ConsoleEventHandler(): Process Detached.
11/29/2001 22:57:30 ConsoleEventHandler(): Caught Shutdown console event .
11/29/2001 22:57:30 ConsoleEventHandler(): Cleaning up and terminating
Process ...
11/29/2001 22:57:38 ConsoleEventHandler(): Caught Shutdown console event .
11/29/2001 22:57:38 ConsoleEventHandler(): Cleaning up and terminating
Process ...
11/29/2001 22:57:38 Error 6 killing thread 346.

And, the dsmsched.log * SAME TIME-->

11/29/2001 22:57:30 ANS1898I ***** Processed    77,500 files *****
11/29/2001 22:57:32 ANS1898I ***** Processed    78,000 files *****
11/29/2001 22:57:34 ANS1898I ***** Processed    78,500 files *****
11/29/2001 22:57:36 ANS1898I ***** Processed    79,000 files *****
11/29/2001 22:57:37 ANS1898I ***** Processed    79,500 files *****
11/29/2001 22:57:38

>>>>>> Process Interrupted!!  Severing connection. <<<<<<
11/29/2001 23:00:37 Querying server for next scheduled event.

Is this USER initiated or AUTOMATICALLY initiated by the system?

>From query event I am seeing the STATUS=RESTARTED after 3 or 4 hours after
processing!

Any insight, comments, ideas, etc... are welcome!

Thanks,


Demetrius Malbrough
UNIX/TSM Administrator

Reply via email to