Check the logging level for the jobs. Logging is specified on the SBMJOB
command or in the job description for the job. An example LOG(4 0 *SECLVL)
will always produce a job log regardless. You can use *NOLIST which should
only produce a job log if the job ends with a severity greater than 0. You
can also increase the severity replacing 0 with say 20 and the you will
only get a job log if the end severity is > 20. While not specifically
about reducing the number of job logs you can also specify LOGCLPGM(*YES)
which can assist in debugging a problem greatly.

Sent from my iPhone

On 19 Dec 2015, at 11:24 AM, tim <iseriesstuff@xxxxxxxxx> wrote:

I have been monitoring qezjoblog output. there are thousands of job logs
in there. many of the logs i see dont really show any errors other then
job completion. There are logs that have sev 40 for example, but after
further looking, they end of being decimal data errors that have the
"monitor" keyword around them so the rpg program doesnt bomb.

Is there a better way to reduce the amount of job logs without loosing
important information?
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
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

This thread ...


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

This mailing list archive is Copyright 1997-2020 by 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].