RE: Logging SQL statements

Vern's right, there's nothing 'easy' about dbmon :)

JDBC & ODBC can be logged via the exit point support without significant
performance hit (we do it in a couple of our tools).  Server side SQL can be
run from many different interfaces (as Rob pointed out) so the only sensible
route there is STRDBMON.  You would want to be selective with DBMON rather
than running it system wide as it can impact performance if your shop drives
a lot of SQL.  Dbmon filtering's also where our tools have value add.

Elvis

-----Original Message-----
Subject: RE: Logging SQL statements

He DID say easy!

Actually STRDBMON and ENDDBMON are the way to go, but the resulting data
file is a bear to work with. Lots of fields overloaded to mean different
things based on different values in other fields - highly not normalized.
There is a paper somewhere at www.iseries.ibm.com/db2 that gives you lots of
queries to help you.

Centerfield Technology is perhaps the main resource for software that does
this kind of thing - www.centerfieldtechnology.com - Elvis Budimlic there
often has posts on this list. I used to work there, as well.

You say you want to log it from emulation - emulation has nothing to do with
SQL directly, so there would be no exit for it - there are exits for ODBC
kinds of access where you could log some stuff, IIRC. Navigator uses JDBC, I
think, so that would probably go through the exit.

HTH
Vern
-------------- Original message -------------- 
From: "DeLong, Eric" <EDeLong@xxxxxxxxxxxxxxx> 

STRDBMON? 

Eric DeLong 
Sally Beauty Company 
MIS-Project Manager (BSG) 
940-297-2863 or ext. 1863 



-----Original Message----- 
From: midrange-l-bounces@xxxxxxxxxxxx 
[mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of Luis Rodriguez 
Sent: Friday, June 09, 2006 8:38 AM 
To: Midrange 
Subject: Logging SQL statements 


Hi, 

Is there any (easy!!) way to log SQL statements when they are entered 
thru 5250 emul. and/or iSeries Navigator? An exit point, perhaps? 

Thanks for your help, 

Luis Rodriguez