×
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 3/25/11 12:57 PM, hockchai Lim wrote:
<<SNIP>> But I just do not understand why the system sending that
inquiry message. The job has already ended, what is the point of
sending that INQ message? <<SNIP>>
But in the original example given, the inquiry message was sent
≈106-seconds *before* the job actually ended. So even though the
inquiry was presumably issued *after* the ENDJOB was requested, the
actual forced-end-of-job transpired the 106-seconds later; i.e. the job
was not "already ended" before the inquiry was sent.
A review of both a trace and [a *seclvl] joblog from a specific
incident would generally clarify what transpired and what is origin for
the difficulty.
Regards, Chuck
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
