Hi Richard!
Again, thank you for your helpful reply!
Teaches me to remember the good old RTFM...
Kindest regards,
Eric van Loon
KLM Royal Dutch Airlines
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Richard Sims
Sent: dinsdag 2 mei 2006 13:09
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: TDP for SQL tracing
Eric - I don't have TDP SQL so no experience in tracing it; but from
what
I have read, I think your problem is that what you have effected
is a tracing spec for the normal B/A client. The TDPs instead use the
TSM API, and a whole different discipline. Try following the Problem
Determination Guide's area "How do I trace the Data Protection client?",
and see if that does the trick.
Richard Sims
On May 2, 2006, at 4:20 AM, Loon, E.J. van - SPLXM wrote:
> Hi *SM-ers!
> I added the trace parameters to the dsm.opt on a client running the DP
> for SQL Server client.
> I added the following lines:
>
> Tracefile d:\tdptrace\tdptrace.txt
> Traceflags stats, options, compress
> Tracemax 100
>
> The tracefile confirmed this:
>
> 05/01/2006 21:30:47.745 : Current trace classes enabled:
> CONFIG, COMPRESS, TIMESTAMP, PREFIX, STATS
>
> But it only contains the CONFIG output. No statistics, no compression
> info, nothing...
> What am I doing wrong???
**********************************************************************
For information, services and offers, please visit our web site:
http://www.klm.com. This e-mail and any attachment may contain confidential and
privileged material intended for the addressee only. If you are not the
addressee, you are notified that no part of the e-mail or any attachment may be
disclosed, copied or distributed, and that any other action related to this
e-mail or attachment is strictly prohibited, and may be unlawful. If you have
received this e-mail by error, please notify the sender immediately by return
e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM),
its subsidiaries and/or its employees shall not be liable for the incorrect or
incomplete transmission of this e-mail or any attachments, nor responsible for
any delay in receipt.
**********************************************************************
|