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
> 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.