I don't think that's the main reason for all the extra stuff in the job log - IF that is what the OP is talking about when he says "entries"! It could also get lots of spooled files of the job log, if the job runs long enough and does enough stuff.
Just running STRDBG in a job that has any SQL will cause all the optimizer messages to be written to the job log.
Actually the analytical tools use the output of the database monitor, and probably NOT job log output. When you start a monitor in Navigator, it doesn't turn on debug, it does a STRDBMON - entirely different thing.
----- Original Message -----
On 9/9/13 7:42 AM, Tom wrote:
I have an SQLRPGLE program which, when run in STRDBG, generates a lot of
qezjoblog entries. Is there some way to stop those qezjoblog entries
from being generated?
I'll bet it does: that's how all the slick GUI analytical tools for SQL
work -- by running queries in the debugger.
No idea how to stop it, though.