|
-- [ Picked text/plain from multipart/alternative ] You might try using a data area that indicates if a process is active or not and have each program look at this data area prior to doing any 'real' processing. If it finds that the data area indicates that a job is currently active, you could put it in a wait state for a period of time, say 5 minutes then check the data area again. Obviously, each program would set the data area to a value (indicating activity) when it is initiated (after it checks to see if is safe to run) and reset the data area at completion. I have used this method very successfully in the past. The only rub comes in at an abend. You then either need some recovery/reset logic built in, or you have to manually reset the data area. Thats my 2 cents. --------------------------------- Do You Yahoo!? Check out Yahoo! Shopping and Yahoo! Auctionsfor all of your holiday gifts!
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.