×
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.
"MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx> wrote on 05/16/2017
12:35:55 PM:
Is there an easy way, short of setting up a private batch job queue, to
force sequential execution?
A new single-threaded job queue is easiest and better on resources
because it keeps subsequent jobs from getting into the active job
subsystem where they will take up resources while they wait (by some other
method) on an active twin to terminate. You *could* use SBMJOB to submit
scheduled jobs and then the active job could release the next scheduled
twin job before the current job terminates, but that is error prone (as
much as any other program-driven method of insuring the single-threaded
nature of these jobs.
Sincerely,
Dave Clark
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
