Statement Event Monitor Data

[jbaker]

I have run an statement event monitor and am digging through the data
it produced. Some of the rows in the stmt table have me perplexed.
These records have a stmt_text that is blank with a stmt_type of 1. I
understand that this means it is a static SQL statement and I can use
the creator, package_name, package_version_id and section_number to
look up the text in the syscat.statements table. In this case though,
these records have no creator or package information and the
section_number is 0.

What is this telling me and how do I find out what the statement
actually is. Since I have 9000 occurances like this and 500 seconds of
run time for one program I consider this significant.
thanks for your help

Jack

[Sean McKeough]

Hmm...section 0 for dynamic sql is a magic section used by DB2 for
internally driving SQL statements (an example is creating the tables
used by a write to table event monitor).

But what you're describing below sounds different (missing section
info?)...is there any way for you to narrow this down to a particular
sql statement? (yeah, I know, that's why you're running the evmon, but
if you could narrow it down we could collect a trace to see what's going
on)...

jb****@marketron.com wrote:

I have run an statement event monitor and am digging through the data
it produced. Some of the rows in the stmt table have me perplexed.
These records have a stmt_text that is blank with a stmt_type of 1. I
understand that this means it is a static SQL statement and I can use
the creator, package_name, package_version_id and section_number to
look up the text in the syscat.statements table. In this case though,
these records have no creator or package information and the
section_number is 0.

What is this telling me and how do I find out what the statement
actually is. Since I have 9000 occurances like this and 500 seconds of
run time for one program I consider this significant.
thanks for your help

Jack