|
We use a keyed file, Chain to a record leave it locked. Other jobs would monitor for the lockwait and know that xxx is already running or being done. We changed our lockwait time to 5 sec for that file. For example we have an interactive program to do production. Only one crew can be doing production for a particular machine number at a time. We chain with machine number, leave it locked, other users will see (via the error message of lock record wait) who is doing production currently. If session ends or what ever, record lock is released. I like it better than Data Area's for this type of thing. john -------------------------------- I don't particularly like the data area approach, but you could create and delete the *DTAARA's in QRPLOBJ. The system does not use this library for data areas, so there would be no conflict there, and it is implicitly cleared on any IPL. Al
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.
midrange.com
