×
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 28-Jun-2016 14:42 -0500, Hayes, Daniel wrote:
<<SNIP>> the joblog.
The selected snippet includes prior to the call of the CLP J04572CCX
from 08:18:47.625592 to the return from that CLP at 08:19:47.497568 as
the apparent first invocation, up until ~08:19:47.64xxxx as the start of
the second invocation. However, the given joblog should include the
return from the CLP J04572CCX spanning the second invocation plus some
[pages] of the messaging that follow, so as possibly to provide greater
context; that could include possibly the next sixty-some seconds, and
probably near that same amount of records\data again [i.e. doubling the
amount selected originally for inclusion], assuming the second
invocation runs similarly as long and verbose as the first invocation.
Note: Consider changing the job(s) that run this application to
specify Job Message Queue Maximum Size (JOBMSGQMX) to 64 to limit the
wrapping effects; see, e.g.: Change Job Description (CHGJOBD).
Possibly, if some code depends on processing old messages, such as a
dependence coded on receiving messages no longer associated with
programs active on the stack, then I suppose the wrapping could be
negatively impacting that processing.
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
