|
Brian & Dawn, In a message dated 97-10-18 08:28:36 EDT, you write: > 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. Unfortunately, the AS/400 doesn't provide an equivalent to the S/36 "IF ACTIVE" OCL function (much to the chagrin of many here, especially given that it is supported in the /36 environment). Most of the books suggest creating a unique data area, and performing a *EXCL ALCOBJ on it when the job in question is running. If other jobs cannot get a lock, then you know the job is running. Given today's client/server environment, I personally find this solution inadequate. However, it should work in your stated case... HTH, Dean Asmussen Enterprise Systems Consulting, Inc. Fuquay-Varina, NC USA E-Mail: DAsmussen@AOL.COM "Sleep, riches, and health, to be truly enjoyed, must be interrupted." -- Jean Paul Richter +--- | 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-2025 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.