> Could you show me how to stop writing this error to log file ?
The short answer: there is no function in TSM to stop writing specific
messages to the log file.
But you are asking the wrong question.
Instead of asking "how can I stop writing this error message to the log
file?", you need to ask, "why is this message being written?"
Here are the messages you are seeing:
02/16/2005 08:31:48 ANS1809W Session is lost; initializing
session reopen procedure.
02/16/2005 08:32:03 ANS1810E TSM session has been reestablished.
02/16/2005 08:52:28 ANS1512E Scheduled event 'CENTER2_BK' failed.
Working your way backwards through the messages, ANS1512E is caused by
ANS1810E. ANS1810E is caused by ANS1809W. As I noted earlier, ANS1810E has
been changed to ANS1810I in newer TSM code. You can install the newer TSM
code so that if ANS1809W is issued, you will instead see ANS1810I. This
will eliminate ANS1512E, and you will get return code 8 instead of 12
(barring any other errors that might occur). However, it still does not
eliminate ANS1809W, whose cause needs to be investigated.
If you do not understand what I wrote above, then I recommend you review
the client manual chapter 7 on automating tasks, which includes a
discussion of return codes and what they mean. This will help you
understand *why* you see return code 12. I also recommend that you make
use of the message documentation, either by looking up the meanings of the
messages in the TSM Messages manual, or by using the "dsmc help" command
to look up the messages. ("dsmc help" is a menu-driven help system for
client commands, options, and messages.)
In sum: there is no way to tell TSM "stop writing message xxx to the error
log". Instead, you need to investigate the cause of message "xxx" and fix
the cause. TSM is telling you there is a problem; TSM itself is probably
not the problem. In this case, the cause for ANS1809W needs to be
investigated. This message is most often the result of some kind of
network problem. Fix the network (or other) problem, and ANS1809W goes
away. If ANS1809W goes away, then ANS1810E (or ANS1810I if you install
newer client code) goes away.
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-02-18
19:03:40:
> Could you show me how to stop writing this error to log file ?
>
> ----- Original Message -----
> From: "Andrew Raibeck" <storman AT US.IBM DOT COM>
> To: <ADSM-L AT VM.MARIST DOT EDU>
> Sent: Thursday, February 17, 2005 12:56 PM
> Subject: Re: Return code = 12
>
>
> > If there are no other error-level messages besides ANS1810E, then
ANS1810E
> > is the culprit. This message should be informational, not error, and
that
> > has been fixed in the latest 5.2.3 interim fix level or 5.3.0.0.
However,
> > the backup will still get return code 8 if ANS1809W (a warning-level
> > message) is issued.
> >
> > 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-02-16
> > 20:26:39:
> >
> > > Dear all,
> > >
> > > I use TSM ver5.2. I view dsmerro.log file and see a lot error
> > > message following :
> > >
> > > 02/16/2005 08:31:48 ANS1809W Session is lost; initializing session
> > > reopen procedure.
> > > 02/16/2005 08:32:03 ANS1810E TSM session has been reestablished.
> > > 02/16/2005 08:52:28 ANS1512E Scheduled event 'CENTER2_BK' failed.
> > > Return code = 12.
> > >
> > > But in dsmsched.log, I also see :
> > >
> > > 02/16/2005 08:52:25 Selective Backup processing of '\\center2-
> > > bk\g$\db_mobifone\*' finished without failure.
> > > 02/16/2005 08:52:28 ANS1512E Scheduled event 'CENTER2_BK' failed.
> > > Return code = 12.
> > >
> > > Pls help me to fix it,
> > >
> > > Thank in advance,
> > >
> > > Nghiatd
> >
|
