× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Chuck, where would one request such an enhancement? I think I requested a RPG enhancement once long ago, but completely forgot where I did that. I'm very familiar with RFE for RDi enhancement requests, is it within that site? I ask b/c I'd love to see your *SUPPRESS suggestion implemented.

-Kurt

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of CRPence
Sent: Monday, September 09, 2013 2:28 PM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: SQLRPGLE in STRDBG creates *a lot* of QEZJOBLOG entries

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.

--
Regards, Chuck
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.