Hi Marcel,
This is a bit of a gray area. Early in the product's life, tracing tended
to be more useful for IBM support and development, but over time, we have
become more conscientious about trying to make trace data more informative
in its own right (where it makes sense to do so). So while we have
externalized some of the trace features, my earlier statement remains
fairly accurate. In your case, I would guess that the part I mentioned
about some tracing being useful for advanced users applies. :-)
I am not involved in the development of the TSM training curriculum, so I
do not know what is provided therein. However, for advanced users who want
to do more of their own diagnostic work before calling IBM for help, I can
say that there is some value in providing information about tracing. For
example, if you want to know "why is this file being backed up by an
incremental operation, I do not think it is changing", the FIOATTRIBS
trace class could very well help you identify what it is about the file
that TSM detects as changed. Or if you are looking to confirm that you are
experiencing certain symptoms of an APAR, it might be possible for you to
run your own trace to see if the symptoms match. As you point out, there
are uses for tracing in performance, that can save you a call to IBM. The
client trace part of the Problem Determination Guide I mentioned earlier
describes less than 25% of the trace classes in the client.
There are more complex problems where a trace by itself is not very
helpful; but when placed in context with the source code (which is not
publicly available, of course), is very useful for IBM support and
development to diagnose problems.
In sum, while tracing has evolved over the years such that it can help
solve problems independent of IBM support, it still remains primarily
something to be used in conjunction with IBM support.
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-24
10:50:28:
> Andy,
>
> On Thu, Feb 24, 2005 at 09:21:39AM -0700, Andrew Raibeck wrote:
> > > where can i find an updated list over flag for TRACEFLAGS???
> >
> > In the Problem Determination Guide I referenced earlier.
> >
> > Just to set proper expectations: In general, tracing is intended to be
> > used only at the direction of IBM support and development for
diagnosing
> > customer problems. While some degree of tracing can be useful for
advanced
> > users, it is not really intended as a fully documented end-user
feature to
> > be used independent of IBM support.
>
> So why does IBM offer a TSM performance course where tracing and all its
> options are discussed? I hope IBM does not force us to take the course
> over and over again just to keep up to date on traceflags and options.
> In other words, It would be nice to have up to date traceflags/options
> publicly available and not just when IBM feels like it...
>
> I just the information form the course a few time to investigate some
> oracle tdp performance problems. Interaction with IBM on every step in
> that case would have taken much to much time. So I was glad the
performance
> course was there...
>
> Regards,
>
> -Marcel
> --
> ======-------- Marcel J.E. Mol MESA
> Consulting B.V.
> =======--------- ph. +31-(0)6-54724868 P.O. Box 112
> =======--------- marcel AT mesa DOT nl 2630 AC
Nootdorp
> __==== www.mesa.nl ---____U_n_i_x______I_n_t_e_r_n_e_t____ The
> Netherlands ____
> They couldn't think of a number, Linux user 1148 --
> counter.li.org
> so they gave me a name! -- Rupert Hine -- www.ruperthine.com
|
