ToddT
Member
I have been asked to open up user security to the managers over specific application areas (i.e. HR, Payroll, A/R, etc.). The managers want the authority to add, modify, and remove users from within OneWorld Xe. They also want to be able to add groups and modify the application security for those groups.
My question is, how could this be accomplished while preventing them from accessing users from other application groups and tracking what they have done just in case they mess up?
We are running OneWorld Xe on an AS/400 and we considered utilizing the AS/400 journaling. The problem being a new journal entry would be created each time there is access to the F0092 and F00950, we would end up taking a performance hit. We performed a test against the F0092 and that alone provided a performance hit.
Any assistance any of you could provide would be greatly appreciated.
My question is, how could this be accomplished while preventing them from accessing users from other application groups and tracking what they have done just in case they mess up?
We are running OneWorld Xe on an AS/400 and we considered utilizing the AS/400 journaling. The problem being a new journal entry would be created each time there is access to the F0092 and F00950, we would end up taking a performance hit. We performed a test against the F0092 and that alone provided a performance hit.
Any assistance any of you could provide would be greatly appreciated.