|
From a work management perspective it's about as easy to implement as itcan get, non-intrusive and reasonably easy to see when you look at it.
I've probably asked a variation on this before:force sequential execution?
Given a system in which the defaults for SBMJOB are set up to run
multiple batch jobs concurrently,
AND given that a series of batch jobs are being spawned off from a CL
program running in a terminal session, that are designed to run
sequentially, and are guaranteed to get into fights with each other if
run concurrently,
Is there an easy way, short of setting up a private batch job queue, to
--
--
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.