|
Dave/Booth, >Another idea might be to have the application's front end put a shared lock >on a specific object, or there may already be a handy object that's always >locked by all users within the application. Then simply retrieve the object >lock details and send a break message to each locking workstation. Since it is obviously an interactive application, why not just use the DSPF associated with the program? It automatically gets shared no-update locks while the display file is open. The QWCLOBJL api documented in the Work Management APIs manual can be used to return the list of current locks to a user space. Doug +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | 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.