×
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.
To which I'll add that child-server jobs are often run as batch jobs
("prestart" appears to be another option, but I haven't the slightest
idea how to do that with something that doesn't come from IBM), but in
an interactive subsystem, from an interactive job queue (because batch
job queues are traditionally set up to run jobs sequentially instead of
concurrently).
And I'll also add that if several distinct batch jobs are DESIGNED to be
run sequentially, rather than concurrently, and the default batch job
queue is set up to run jobs concurrently, then you can end up with the
"later" jobs getting the data before the "earlier" ones had finished
with it (which can be bad). On the other hand, if the default batch
queue is set up to run jobs sequentially (the traditional way), and a
batch job locks up without anybody bothering to check on it, it can tie
up the batch queue (which can also be bad).
--
JHHL
As an Amazon Associate we earn from qualifying purchases.
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
