|
Create a file with a single record, set the "Locked Wait" time to 5 seconds. (or something small). In the batch job chain to the record and hold it locked for update for the whole job. In the second job, Chain and if you have an error on the chain(Use an error indicator on the chain statement) the other batch job is active. No matter how the batch jobs end, the lock will be released. Its better than setting some flag that gets "Stuck *ON" if a job ends in error. John Carr CDP EdgeTech >Greetings All; >I have a situation where I have a batch job that needs to know if another batch job is running, so that if it is, the first batch job will abort only a portion of the run. > >Any Idea's? > >Brian & Dawn Stapleton >BStapleton@ameritech.net +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to "MIDRANGE-L@midrange.com". | To unsubscribe from this list send email to MAJORDOMO@midrange.com | and specify 'unsubscribe MIDRANGE-L' in the body of your message. | Questions should be directed to the list owner/operator: david@midrange.com +---
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.