|
Both have some merit. However think of the steps involved. 1 - Find out what users are using the files. 2 - Get the users out. 3 - Keep them out. By far, the most draconian method is ENDSBS *ALL *IMMED which brings your system into a restricted state. It's 100% effective, but you may not choose to go that route because you may want to allow some processes to continue while you deal with a subset of files. Disabling the user profiles will not get the users out who are already using the files. It will stop new users. Then again, if you're handling a subset you're effectively locking that user out of everything. If you're a smaller shop then locking the users may not be necessary because you could - attempt to lock the object, - if unable because someone else has a lock, find out who they are and end their job - repeat until successful A larger shop may continuously have people getting back on in between those steps and may need to disable related user profiles. Then you get into minutia about how to handle people who were previously disabled, like, you may not want to automatically enable them at the completion. There's a book called "Backup and Recovery Guide" that may be a big assistance. It's rather thick. Rob Berendt
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.