Re: SQLRPGLE in STRDBG creates *a lot* of QEZJOBLOG entries

Tom

This might almost be a nice option on the STRDBG command, instead of requiring some entry in the QAQQINI, which is relatively less simple to manage for things like this.

So that would make a nice requirement to submit - you'll want to say what benefit it gives you, like what you've described here in this post.

HTH
Vern

----- Original Message -----
Thanks Chuck!

1. Yes, many spool files are produced and enqueued to the qezjoblog
outq. Sometimes many, many thousands of spoolfiles. I don't need any of
them.

2. Yes, I would like to suppress entirely the action/process that is
causing the spoolfile entries for exactly the reason you mention - since
I've tested the SQL queries in interactive SQL, I have no interest in
debugging the SQL queries, just the non-query stuff.


TomH

p.s. - though not mentioned, before asking I did a Google search (using
qualifier "site:midrange.com") for terms related to my request but I
reckon I didn't hit on the right combination.


On 9/9/2013 2:28 PM, CRPence wrote:

On 09 Sep 2013 07:42, 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?

Explicitly define "qezjoblog entries". Does that mean to imply many
QPJOBLOG spooled files are produced and enqueued to the Output Queue
(OUTQ) named QEZJOBLOG? If so, then refer to the job settings for "Job
message queue full action" (JOBMSGQFL) [system value QJOBMSGQFL] and
"Job message queue maximum size" (JOBMSGQMX) [system value QJOBMSGQMX],
and possibly the Control Job Log Output (QMHCTLJL) that "controls the
production of a job log when the related job ends or when the job
message queue becomes full and the print-wrap option is in effect for
the job."

If the concern is to suppress entirely the SQL and Query Engine debug
messages from being issued while debug is active, as I have noted in
prior messages, probably best to ask for an enhancement to the QAQQINI
to effect a *SUPPRESS of the Query Debug Messages; i.e. articulate that
the desire is to debug jobs that perform query activity without the
effects of the Query Debug Messages, because for example, there is no
interest in debugging the queries, just the non-query stuff. There may
already be some support for limiting those debug messages, but the same
topic\discussion has occurred several times in the past [at least two
very recently], but I do not recall anyone ever mentioning any means to
do so.