ADSM-L

Re: ANS2820E Mystery Message

2005-04-05 15:53:15
Subject: Re: ANS2820E Mystery Message
From: Mike Bantz <mbantz AT RSINC DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Tue, 5 Apr 2005 13:52:51 -0600
Nope - not a mystery reboot, just a user killing the backup.

:-)

Richard, for your QuickFacts:

ANS2820E An interrupt has occurred. The current operation is interrupted
by a break signal such as CTRL-BREAK or CTRL-C.
System Action: The TSM operation and process are ended immediately.
User Reponse: Restart the operation if desired.

I assumed that when a user wants to have their backup run at a certain
time they'll let it continue unmolested. Chalk this one up to
"everything worked as designed, aside from plain old verbal
communication with the node owner".

Mike Bantz
Systems Administrator
Research Systems, Inc
4990 Pearl East Circle
Boulder, CO 80301
(303) 413-3999 direct
(303) 786-9909 fax
http://www.researchsystems.com


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Andrew Raibeck
Sent: Tuesday, April 05, 2005 12:45 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: ANS2820E Mystery Message

Maybe there was a mystery reboot.   :-)

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.

"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 2005-04-05
11:07:42:

> Well, if Richard Sims' QuickFacts lists the following for this error, 
> then I'm not sure where else to turn:
>
> ANS2820E An interrupt has occurred. The current operation will end and

> the
>          client will shut down.
>         Mystery message in TSM 5.3.  Reported to occur in the 
> dsmserror.log and
>         dsmsched.log, when the scheduler concludes.
>
> I've got this on a machine from last night's backup. 5.3.0 client on 
> an XP SP2 node in the dsmsched log, 5.2.0.2 on a Win2k server . This 
> was coupled with a missed schedule window for that node.
>
> Anyone ever heard anything more addressing the mystery behind this 
> error?
>
> (and that resource still rules, Richard!)
>
> Mike Bantz
> Systems Administrator
> Research Systems, Inc
> 4990 Pearl East Circle
> Boulder, CO 80301
> (303) 413-3999 direct
> (303) 786-9909 fax
> http://www.researchsystems.com <http://www.researchsystems.com/>
>

<Prev in Thread] Current Thread [Next in Thread>