Generally you can check the first job log produced and it will show the
error if in fact an error that goes into MSGW occurs. Even errors that do
not cause an abend can generate multiple spooled files (i.e. Date
conversion errors that are being monitored by the program)
From: "Steinmetz, Paul" <PSteinmetz@xxxxxxxxxx>
To: "'Midrange Systems Technical Discussion'"
Date: 08/14/2014 11:03 AM
Subject: RE: Multiple joblogs being created for some jobs
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>
All jobs set as below, system defaults.
Job message queue maximum size . . . . . . . . . : 64
Job message queue full action . . . . . . . . . . : *PRTWRAP
It must something in the job?
How would I find that?
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Sent: Thursday, August 14, 2014 11:37 AM
To: Midrange Systems Technical Discussion
Subject: Re: Multiple joblogs being created for some jobs
There are system values for what happens when the job message queue gets
The first is the max size in MB, the second is the action when full. One
action is *PRTWRAP - it'll print a job log, then continue from there.
These are also in JOBDs and SBMJOB.
Now it could also be that the program is printing job logs at certain
On 8/14/2014 10:28 AM, Steinmetz, Paul wrote:
Normally, only one joblog is created for a job.
Some jobs have multiple joblogs being created.
Is there a system, profile, job, etc setting that would cause this?
In one instance 159 joblogs were created for a single batch job, each
about 80 pages, or 584k.
The final joblog is 5,164 pages, 32,792k.
IBM i Systems Administrator
Pencor Services, Inc.
462 Delaware Ave
Palmerton Pa 18071
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