×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
On 14-Aug-2014 13:10 -0500, Steinmetz, Paul wrote:
<<SNIP>>
Creation times for the joblogs are every 21 seconds.
There is no overlap.
The beginning and end time of each message does not match the
creation time of the QPJOBLOG.
Only the final 159 spoolfile matches.
The final joblog is 62 times larger (5,164 pages) then 2 thru 158
(81 pages)
<<SNIP joblog details; apparently from /final joblog/ per EOJ msg>>
What were the logged [and not filtered] messages in each of the
spooled QPJOBLOG produced in response to [each of] the CPI2417 messages
sent to the history log (QHST), would be of the most interest. What was
in the final spooled joblog are not of much interest, with regard to
finding the possible origin of the CPI2417.
If each of the 81-page joblogs are effectively identical, but only a
couple CPI2417 were issued, then I would be suspicious that all of them
were the result of the CPI2417; that there might be some defect whereby
the CPI2417 is not properly being issued for every case.
If a job will be known to reproduce the condition of the multiple
joblogs [including some for CPI2417], then as described in another
reply, using servicing\debug can very easily assist to determine the
origin for the [non joblog-server-produced] spooled QPJOBLOG files for a
job; that includes probably identifying any that might be a result of
the condition diagnosed by CPI2417, even if that message is
[unexpectedly] not being sent.
This mailing list archive is Copyright 1997-2024 by midrange.com 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].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
