467,907 Members | 1,075 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 467,907 developers. It's quick & easy.

Finally: SQL procedure tracing

Hi SQL Procedure developers,

As threatened in earlier posts the SQL PL Tracing facility is finally
oot-and-aboot.

SQL procedure tracing: Analyzing SQL procedure flow
This article describes an API that allows for transparent tracing of SQL
procedures as well as explicit tracing of non-SQL procedures in DB2
Universal Database (UDB) V8.2 for LUW. An example SQL interface to this
API is provided, as well.

http://www-106.ibm.com/developerwork...lau/index.html

Feedback is much appreciated.
I want to keep the ball rolling on this one :-)

Cheers
Serge
Nov 12 '05 #1
  • viewed: 1487
Share:
3 Replies

"Serge Rielau" <sr*****@ca.eye-bee-em.com> wrote in message
news:41********@news3.prserv.net...
Hi SQL Procedure developers,

As threatened in earlier posts the SQL PL Tracing facility is finally
oot-and-aboot.

SQL procedure tracing: Analyzing SQL procedure flow
This article describes an API that allows for transparent tracing of SQL
procedures as well as explicit tracing of non-SQL procedures in DB2
Universal Database (UDB) V8.2 for LUW. An example SQL interface to this
API is provided, as well.

http://www-106.ibm.com/developerwork...lau/index.html
Feedback is much appreciated.
I want to keep the ball rolling on this one :-)

One small nit, Serge. In reading the Installation section of the article and
saw:

You are on a Windowsģ 32-bit system or Linux Intel 32-bit:
1.. download the respective zip file and extract it
My immediate thought was that there was no information about what specific
file to download and there was information about where to find it. That was
frustrating. It wasn't until I got to the end of the article and found the
Download section that I realized you *had* provided the files.

An impatient reader *could* have the same thoughts that I did when starting
the article but give up and not bother with trying to trace his SQL
procedure because information about the key files *appeared* to be missing.
Therefore, I think the article would be stronger if the download links were
more visible; perhaps you could move the Download section into or just
before the Installation section or provide an internal link to it from point
a) 1) of the Installation instructions.

I also think it would be a good idea to put a Download link in the Contents
part of the page; that's the first place I looked after starting the
Installation section and when I didn't see Download, I thought you'd
forgotten to provide any information about where to find the files.

Aside from that, the article seems pretty good although I won't be able to
say for sure until I upgrade to V8.x and have a chance to try your
suggestions myself.

Rhino
Nov 12 '05 #2
Rhino,

Thanks for the feedback. The template is actually standard, but I can do
two things:
1. Pass the general comments on to the Editor to update the template
2. Add some text (or link) to get my article fixed in particluar.

Cheers
Serge
Nov 12 '05 #3
Serge Rielau wrote:
Rhino,

Thanks for the feedback. The template is actually standard, but I can do
two things:
1. Pass the general comments on to the Editor to update the template
2. Add some text (or link) to get my article fixed in particluar.


Serge, I usually add some text in the article itself that explicitly
mentions the "download section below".

--
Knut Stolze
Information Integration
IBM Germany / University of Jena
Nov 12 '05 #4

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

2 posts views Thread by James Foreman | last post: by
reply views Thread by Paul Ibison | last post: by
6 posts views Thread by serge calderara | last post: by
2 posts views Thread by deepukutty | last post: by
reply views Thread by cnys | last post: by
reply views Thread by rehto | last post: by
4 posts views Thread by Prashant Sogarwal | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.