Previous Topic: Define Profiles By ApplicationNext Topic: Define Profiles By Job Description


Override Strategy

If you choose to use the default options of the AUTH control option, you can use override strategy in designing your profiles.

Example: override strategy

PROFILEA can be defined to allow READ access to system minidisks. PROFILEB can be defined to allow UPDATE access only to a critical subset of minidisks defined by PROFILEA. A user attached to PROFILEB and PROFILEA in the following order, has UPDATE access to the critical minidisks, and READ access to the remaining minidisks, where the access has not been overridden by PROFILEB.

PROFILEB
PROFILEA

Additionally, other users who only require READ access to system minidisks can simply be attached to PROFILEA.

Due to this override capability, profiles are always attached to users in the order ranging from the profiles that are most specific to their particular needs to the profiles containing the more general access requirements, since the specific ones override the more general.