Comments on: TVD$XTAT 4.0 Beta 9

By: Christian Antognini

Christian Antognini — Thu, 31 Mar 2011 15:20:56 +0000

I must admit that the current implementation is not complete. So, yes, it will be improved…

Thank you for the feedback,
Chris

By: Yuri

Yuri — Thu, 31 Mar 2011 13:59:57 +0000

Hi Christian,

I accidentally discovered that TVD$XTAT aggregates similar queries and shows them as one in its report. Similar queries are those which are differed in literals only. Maybe it will be useful to warn about this.

By: Christian Antognini

Christian Antognini — Tue, 08 Jun 2010 16:27:12 +0000

Hi Andy

> but I don’t have text.xsl

Yeap. It was still not available with Beta 9. That said, I have a first alpha release. I’ll send it to you by email.

> can I easily create one ?

Difficult to say whether it’s easy or not. It all depends on the amount of data and the format. But, basically, you can do it. In the file tvdxtat.xsd you can see the structure of the XML file. The XLS file has to take it as input an extract/format the output as you like.

Cheers,
Chris

By: Andy Helm

Andy Helm — Tue, 08 Jun 2010 14:25:09 +0000

Christian,
the TVD$XTAT usage message indicates there is a -t option to select an XSL template, hinting that html.xsl and text.xsl are choices. html.xsl is shipped with TVD$XTAT, but I don’t have text.xsl
It would be useful for me to be able to post process the TVD$XTAT output, to compare some critical timings from multiple runs of a test suite – is text.xsl available, or can I easily create one ?

By: David Mann

David Mann — Wed, 18 Nov 2009 15:36:03 +0000

Thanks for releasing this program, after using it for 2 weeks it is my preferred .TRC file post processing tool!

By: Christian Antognini

Christian Antognini — Tue, 25 Aug 2009 16:21:21 +0000

Hi Haris

The only reason I can think of is that you don’t have wait events in the trace file. It is the case?
(If yes, you should have a warning in the section “Interval” at the beginning of the output.)

Cheers,
Chris

By: Haris

Haris — Tue, 25 Aug 2009 02:56:24 +0000

Hi Christian

The output file reported “unaccounted-for” under Component column which shows 99.594%. What is “unaccounted-for” means and how do i move forward from there?

Please advice.

Regards
Haris.

By: Roberto

Roberto — Wed, 22 Apr 2009 13:34:23 +0000

Ok, It works.
I enclosed the path TVDXTAT_HOME with quotes because of the spaces,
but windowz interpreted (rather strange for me) the quotes as
belonging to the string.
While setting variables, spaces are took into account even without
quotes (furthermore strange for me).
On following commands, instead, quotes are mandatory for words tokenizing.

By: Christian Antognini

Christian Antognini — Sat, 18 Apr 2009 08:44:41 +0000

Ciao Roberto

Mhmm… on my notebook (Windows XP Professional SP3) if I remove the quotes the script no longer works… i.e. I get an error.
Which version of Windows do you use?

Thanks,
Chris

By: Roberto

Roberto — Thu, 09 Apr 2009 13:10:25 +0000

On Windows systems, tcdxtat.cmd doesn’t work. You must remove the quotes around the variables, e.g:
%JAVA_HOME% don’t “%JAVA_HOME%”