This job normally has a very small job log. When I run the job with debug mode on, the embedded SQL RPG runs is loading up the job log. My educated guess is that it is only when the job wraps that these extra job logs show up. They do not appear in a normal run of the job.
I was hoping there would be a setting somewhere driving this. If not, I can live with it since it only happens in testing. I was just curious.
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of CRPence
Sent: Tuesday, August 20, 2013 12:45 PM
Subject: Re: Job Log Wrap creating small job logs
On 20 Aug 2013 09:59, Anderson, Kurt wrote:
Our jobs run using *PrtWrap. We just had a job wrap. It created
around 50 small job logs (just over 400 pages each). The final job
log was 26k pages. I only had one job log wrap message.
Is that a statement of what is found in one of the joblogs, or what was found in DSPJOB JOB(jobnbr/jobuser/jobname) covering the start until the completion of the job?
So my question is why do I end up with 50 small job logs? I've seen
jobs where we had multiple wraps and had 100's of small job logs
before the final large job log.
Joblogs can be spooled for reasons other than just *PRTWRAP. Any request to DSPJOBLOG OUTPUT(*PRINT) suffices. Also the number of logged messages and the resulting spool file size is not fixed for a wrapped joblog. The space for messaging can be used up with very few or even very many messages which remain to be included in the logging.
Is there something I can do so in this case I end up with 2 job logs,
the first being generated before the wrap, and the latter being
everything that comes after? I'm on IBM i 7.1.
If the effect is truly from *PRTWRAP, then not while keeping that same job attribute. However there is an API to control job logging; to an output file. I have mentioned it a few times here in the past; I am too lazy to look it up presently.
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