One job for now.
Not looping job ends find.
I ran a TAATOOL SCNALLSRC2, looking for 'PGM(QMHCTLJL)' 'DSPJOBLOG'
Got 4 hits for DSPJOBLOG, but not for job that is running.
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Mark S Waterbury
Sent: Thursday, August 14, 2014 2:53 PM
To: Midrange Systems Technical Discussion
Subject: Re: Multiple joblogs being created for some jobs
Are you seeing more or less the same messages repeated over and over again, in these job logs? Perhaps for some reason a program is stuck in a "loop" on this one system LPAR, that is not happening on the other "production" system?
On 8/14/2014 2:44 PM, Steinmetz, Paul wrote:
With logging set to 4, 0, *MSG, Log CL *yes, could there messages that are within the job that don't appear in the joblog, thus filling up the job message q, causing the message to wrap.
But then I should have seen 158 CPI2417 - Job message queue for 978872/TRP1/S001NITE19 has been wrapped.
There must be something else that I am missing.
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