|
Hello, we've just started using SEQUEL and have a decision regarding security that I'd like some input on, if possible. We have a library that's always been public *exclude (access via AA - adopt authority, no that AA), and we want to allow users to access it as *use only so they can use SEQUEL to query it. How have you allowed giving users access read only to a library without updating the authority/autl's? We have dozens of grpprf's and hundreds of usrprf's and not all the mbr's of the grpprf's will get access to SEQUEL. I was thinking of creating a signle usrprf (called SEQUEL) with *use and then using the SEQUEL profile swapping program. Is that what you SEQUEL admins have done for this access, or is there another (hopefully simple) way? Also, giving SEQUEL access to a few hundred users, any impact performance-wise. Are there any tips to avoiding performance issues when running SEQUEL for many users? Thanks, Frank ________________________________________________________________________ Check out the new AOL. Most comprehensive set of free safety and security tools, free access to millions of high-quality videos from across the web, free AOL Mail and more.
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.