ADSM-L

Re: [ADSM-L] Ang: Re: Help tracking down spurious "Failed 12"

2011-11-03 09:09:02
Subject: Re: [ADSM-L] Ang: Re: Help tracking down spurious "Failed 12"
From: Zoltan Forray/AC/VCU <zforray AT VCU DOT EDU>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Thu, 3 Nov 2011 09:00:08 -0400
We had the same problem with a Windows box when the client was upgraded
from 6.1 to 6.2.  The help file from the previous version was left behind
and caused errors.  Replaced it with the same version installed by the
newer client (but into a different sub-directory)


Zoltan Forray
TSM Software & Hardware Administrator
Virginia Commonwealth University
UCC/Office of Technology Services
zforray AT vcu DOT edu - 804-828-4807
Don't be a phishing victim - VCU and other reputable organizations will
never use email to request that you reply with your password, social
security number or confidential personal information. For more details
visit http://infosecurity.vcu.edu/phishing.html



From:   Lindsay Morris <lindsay AT TSMWORKS DOT COM>
To:     ADSM-L AT VM.MARIST DOT EDU
Date:   11/02/2011 09:22 PM
Subject:        Re: [ADSM-L] Ang: Re: Help tracking down spurious "Failed
12"
Sent by:        "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>



We have the same issue.  In our case, it's caused by a corrupt or
mismatched dscenu.txt file, causing "ANS0106E message index not found for
message..." in dsmerror.log.

To fix it, we stop the TSM scheduler (no need for that if you're using CAD
I guess), replace the dscenu.txt file with a good one from a client that
is
NOT giving you RC 12s, and restart the scheduler. Works for us anyway.
--------------------
Lindsay Morris
CEO, TSMworks
Tel. 1-859-539-9900
lindsay AT tsmworks DOT com


On Fri, Aug 26, 2011 at 12:37 PM, Andrew Raibeck <storman AT us.ibm DOT com>
wrote:

> An in-use file should not cause an RC 12. Either you are running an old
> client level with some defect that issues the wrong return code (for
> example, see go to the URL in my sig and search for IC35763); or there
is
> some additional error being thrown that causes the RC to be set to 12.
> Examine your dsmerror.log and dsmsched.log files very carefully for any
> other ANSnnnnE or ANSnnnnS messages that might trigger the RC 12. Also,
see
> my other recent posts on this topic.
>
> Best regards,
>
> Andy Raibeck
> IBM Software Group
> Tivoli Storage Manager Client Product Development
> Level 3 Team Lead
> Internal Notes e-mail: Andrew Raibeck/Hartford/IBM@IBMUS
> Internet e-mail: storman AT us.ibm DOT com
>
> IBM Tivoli Storage Manager support web page:
>
>
http://www.ibm.com/support/entry/portal/Overview/Software/Tivoli/Tivoli_Storage_Manager

>
> "ADSM: Dist Stor Manager" <ADSM-L AT vm.marist DOT edu> wrote on 2011-08-25
> 09:26:24:
>
> > From: Jimou <tsm-forum AT BACKUPCENTRAL DOT COM>
> > To: ADSM-L AT vm.marist DOT edu
> > Date: 2011-08-26 12:15
> > Subject: Ang: Re: Help tracking down spurious "Failed 12"
> > Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT vm.marist DOT edu>
> >
> > Hi
> > I wonder why we can have a RC =12 for a skipped file in use,
> > cause there http://www.dsi.upmc.fr/dsi/doc/stockage/clients-tsm/
> > tsmwin/ans60012.htm
> > i see that it should be RC=4
> >
> > But i also have a RC=12 and the only message i got is "in used file".
> >
> > Someone could explain to me why it is not a RC=4 ??
> > Ty in advance.
> >
> >
+----------------------------------------------------------------------
> > |This was sent by jm.faidy AT gmail DOT com via Backup Central.
> > |Forward SPAM to abuse AT backupcentral DOT com.
> >
+----------------------------------------------------------------------
>

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