Re: Locking everybody out of an application database library -- MIDRANGE-L

Subject: Re: Locking everybody out of an application database library
From: Nick Litten <nick@xxxxxxxxxx>
Date: Mon, 4 Jan 2010 11:11:31 -0500
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

Trouble is you cannot lock the library object itself... you need to lock the
individual objects within the library or change system authorities to exlude
everyone.

Of course you could simply rename the LIB while your doing things
exclusivly: LIBx becomes LIBINUSE means that any processes trying to access
objects in LIBx will not be able to until you finshed with and renamed it
back to LIBx

Obviously you will need to monitor for LIBx not being found and stick out a
nice friendly 'in use come back later' error message.

Dirty but effective ;)

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: Locking everybody out of an application database library , James H. H. Lampert

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.