Someone else posted on this thread the link to the TSM Problem
Determination Guide, which includes info on tracing.

But I sure don't know enough about the problem to advise you on what to
trace, i.e. what does "fails" mean? What message are you seeing in
dsmsched.log, dsmerror,log, or stdout, that coincide with the failed
operation? How about on the TSM server? What versions of client and server
are you running, and on what operating systems? Need specifics here.
Again, if we knew more about the nature of the problem, you might not even
need to trace at all. If you just want to know on what file, then I would
think that dsmsched.log or stdout would show you this, or at least give
you a rough idea if the failure occurs consistently in the same place. But
tracing as the first step in diagnostics is ill-advised, and if you were
call in to support and I were working with you, it would not be the first
thing we would do, just as I would not agree to start exploratory surgery
unless I already had a pretty good understanding of my patient's symptoms.
***


*** Note: This is just an analogy, I am not practicing medicine.

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 11/03/2004
09:17:22:

> I am currently trying to backed up a directory with about 3 million
> files in it.  The problem I am having is that is gets to a point and
> then fails at about 2.3million files.  I was hoping to trace this
> problem and find out if it was failing on a particular file.  So how
> would I set a trace for this...
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf 
> Of
> Andrew Raibeck
> Sent: Wednesday, November 03, 2004 10:01 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: TRACING
>
> Normally tracing is most useful when working with IBM support or
> development to diagnose a problem. The trace settings you need, and what
> components you need to trace depend on the nature of the problem.
>
> Perhaps if you were to describe your TSM environment and the problem you
> are having, and include actual documentation showing the problem,
> someone
> on this list might already know what you are seeing, eliminating the
> need
> to trace at all.
>
> 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.
>
>
>
> "Lepre, James" <JLEPRE AT NECA DOT ORG>
> Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
> 11/03/2004 07:20
> Please respond to
> "ADSM: Dist Stor Manager"
>
>
> To
> ADSM-L AT VM.MARIST DOT EDU
> cc
>
> Subject
> Re: TRACING
>
>
>
>
>
>
> Version 5.2.2.2
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf 
> Of
> David E Ehresman
> Sent: Wednesday, November 03, 2004 8:17 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: TRACING
>
> The synax will differ depending on your version of TSM.
>
> >>> JLEPRE AT NECA DOT ORG 11/2/2004 11:56:10 AM >>>
> Hello All,
>
>  I am having a difficult time setting up a trace.  I need to trace a
> backup I am trying to perform because it keeps failing in the same
> place.  I know I need to add something to the DSM.OPT file but I have
> forgotten what it is, and also is there something on the server side I
> need to do as well.  Any help is always appreciated, and thank you in
> advance.
>
> Thanks
>
> James