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

On 09 Sep 2013 13:22, Tom wrote:

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.

Seems probable that changing from *PRTWRAP to *WRAP for the "Job message queue full action" (JOBMSGQFL) [system value QJOBMSGQFL] job attribute could be helpful. And probable that changing the "Job message queue maximum size" (JOBMSGQMX) {may only be available in the *JOBD vs the job} [system value QJOBMSGQMX] could be helpful alone or in conjunction with the prior change.

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.

Submit a Design Change Request (DCR). Others have alluded to the having the same desire in the past, here, but if they made their desire known to IBM is unknown to me, as nobody followed up saying they had. And there is no publication of submitted DCRs that I am aware of.

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.

Probably best to avoid searching QEZJOBLOG which is not germane; concentrating instead on only tokens like SQL STRDBG DEBUG MESSAGES, but then trying to whittle that down to those that include something like PREVENT or SUPPRESS or FILLING or WRAPPING with regard to an action verb, expressing either the desired effect or the undesirable effect. Regardless, the two recent and two older messages:

http://archive.midrange.com/midrange-l/201309/threads.html#00071
"suppress sql joblog messages while in debug mode" ~04-Sep-2013

http://archive.midrange.com/midrange-l/201306/threads.html#00358
"SQL Filling Job Log" ~07-Jun-2013

http://archive.midrange.com/midrange-l/201007/threads.html#00888
"Preventing SQL debug messages" ~30-Jul-2010

http://archive.midrange.com/midrange-l/201005/threads.html#00399
"Reason(s) for SQL generating debugging messages" ~13-May-2009

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.