|
on 10/18/97at 05, the Great and Grand Wazir Brian & Dawn Stapleton <bstapleton@ameritech.net> said: 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. One choice would be for you to go into the other batch job's critical point and create an empty file. As a last step in the other job, delete the batch file. Then the new job can check for the existance of the other file and then a) go on; or b) get out. Another way would be to create a named data area (CRTDTAARA name) and let the other procedure insert "busy" into position 1 thru 4 while it is running and "----" at the end of the job. Then you can retrieve the field in either your CL or RPG program. (I said "busy" but of course you might rather have the job number, the user's name, the time and date, or a small statement of praise for the programming staff.) ---------------------------------------------------- Booth Martin --------------------------------------------------- +--- | 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.