× 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 Wed, May 21, 2014 at 5:09 PM, franz9000 <franz9000@xxxxxxxxx> wrote:
I'll be the one to disagree.
It's my choice to put the jobq on hold, for whatever reason.

I don't think that was the question. The *job* was put on hold, not
the queue. In the case of a single held job, the prevailing view is
that not submitting any further instances of the same job makes the
most sense. I agree with this. If the *queue* is on hold (and the
job itself is released), then I probably would agree with you that new
instances should be submitted freely.

Why should AJS make it's own decision (by design) not to submit,
when the scheduler is running and the time arrives? It has no
application knowledge to know if that is a good idea or not.

Of course no scheduler will have application knowledge. But in the
case of one *job* being held, the odds are that not submitting further
instances of that job (even if it turns out that it was safe to submit
them) is less costly than submitting further instances when in fact it
is not safe to submit them.

John Y.

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.