|
How's about using the various work management api's etc. to find out if anyone has a lock on certain objects, like the library(ies) in question. Any jobs that have a lock, nuke them. That should get any offending showcase people, or any other C/S based application. I would not run the job with a user that uses a job description that puts that library into the library list, unless you massage the library list for that job prior to checking for locks. Otherwise you'll end up committing job suicide - it'll have to kill itself to remove the lock. Rob Berendt -- "All creatures will make merry... under pain of death." -Ming the Merciless (Flash Gordon)
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.