|
Using subsystems to limit the time a user has access is not that great a use of system resources - you can just as easily end the offending users job as the subsystem. Do different shareholders have different times when they can access the system? If not, you could create one subsystem for all the shareholders. Also, the security tool kit (part of V3R7 and V3R2) can enable and disable user profiles on a schedule - this can prevent people from signing on when they shouldn't (GO SECTOOLS, option 6). Five subsystems probably won't hurt, but it sounds like a bad way to start - what happens when it gets up to 10, 20, 100? Better to adopt a strategy that will work for one user or 1,000! Maurice Langeveld wrote: > > The IT Service Delivery manager suggested it, I can see his problem when > we wo'nt do this, because we will give them limeted access, you can just > shut down the subsystem and no problem at all, w'll have to create about > 5 extra subsystems in the beginning. > > What's you're suggestion, secure this on userlevel???? > > Or do you have other suggestions??? > > Greetz, > > Maurice. +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to "MIDRANGE-L@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.