I don't think this kind of thing is a candidate for RFE submission - it's not anything to do with IBM Rational software products. It's more of a system thing.
You have a couple options.
1. Submit a DCR - design change request - Rob has done a lot of those and has spoken of them here several times. That is something coming from an individual.
2. Go to www.common.org and click on the community tab - if you are already a member, just log in, then go to the link for adding requirements. If not a COMMON member, you can still get a login for this purpose. Those get vetted by the CAAC - COMMON Americas Advisory Council - we just recently got completely caught up in carrying requirements to IBM, although we've not got the COMMON side updated to reflect that in every case. Working on that.
DCRs are like RFE, except you mail them in or some other thing - there's a form to fill out.
The COMMON requirements are given much weight, as well, according to a Steve Will, because they are reviewed by a group of people, hence the vetting is trusted quite a bit.
----- Original Message -----
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.
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of CRPence
Sent: Monday, September 09, 2013 2:28 PM
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.
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,
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l